context-loader-be1e10 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited context-loader-be1e10 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Load relevant memories from Pensyve at the start of a session to provide cross-session continuity. Supports summary and full loading modes.
When this skill is invoked (typically at session start via the SessionStart hook), follow these steps:
Check for a mode argument if provided:
pensyve_recall to search memories on demand."If no mode is specified, default to summary.
Run the following pensyve_recall queries to gather session context:
pensyve_recall with query "decided" (limit: 5)pensyve_recall with query "issue OR bug OR error OR problem" (limit: 5)pensyve_recall with query "workflow OR pattern OR process" (limit: 5)pensyve_recall with query "*" (limit: 10) -- broad query to capture recent memories by recencyDeduplicate results across queries (same memory ID should appear only once).
#### Summary Mode (10-15 lines max)
Present a concise briefing with the most important items:
Session Context (from Pensyve memory)
>
Recent Decisions:
>
- auth-service: Using RS256 for JWT signing to support key rotation - api-design: POST endpoints return 201 with created resource
>
Known Issues:
>
- database: Migration script requires Python 3.11+
>
Active Patterns:
>
- testing: Integration tests need tmpdir cleanup after filesystem operations
>
_Use pensyve_recall to search for specific memories._Rules for summary mode:
#### Full Mode (comprehensive)
Present a detailed briefing with scores and metadata:
Session Context (from Pensyve memory)
>
Recent Decisions (3 found): | Entity | Decision | Confidence | When | |--------|----------|------------|------| | auth-service | Using RS256 for JWT signing | 0.9 | 2026-03-15 | | api-design | POST endpoints return 201 | 0.9 | 2026-03-14 | | database | SQLite for MVP, migrate to Postgres later | 0.9 | 2026-03-12 |
>
Known Issues (2 found): | Entity | Issue | Confidence | Score | |--------|-------|------------|-------| | database | Migration requires Python 3.11+ | 0.8 | 0.91 | | cache | Invalidation race condition on concurrent writes | 0.8 | 0.85 |
>
Workflow Patterns (1 found): | Entity | Pattern | Confidence | Score | |--------|---------|------------|-------| | testing | Integration tests need tmpdir cleanup | 0.7 | 0.78 |
>
Recent Activity (5 unique memories, most recent first): | Type | Entity | Summary | Score | |------|--------|---------|-------| | semantic | auth-service | RS256 JWT signing | 0.92 | | episodic | database | Debugged migration failure | 0.88 | | procedural | deploy | Run tests before deploy | 0.75 |
>
_Total memories loaded: 11 | Usepensyve_recallfor targeted search |pensyve_inspectfor entity details_
Rules for full mode:
pensyve_remember to start building context."pensyve_recall queries fail but others succeed, present the successful results and note the failures briefly.PENSYVE_API_KEY environment variable and MCP configuration."~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.