Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/sepehrbayat/sepcc/verify-contextgit clone --depth 1 https://github.com/sepehrbayat/SEPCCWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/sepehrbayat/sepcc/verify-context)<a href="https://agentmods.dev/commands/sepehrbayat/sepcc/verify-context"><img src="https://agentmods.dev/badge/commands/sepehrbayat/sepcc/verify-context.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00090 |
| Opus 5 | $0.00000 | $0.00045 |
| Sonnet 5 | $0.00000 | $0.00018 |
| Haiku 4.5 | $0.00000 | $0.00009 |
Grade B, and why
verify-context scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
- `.mcp.json` has Token Savior as the baseline code retrieval server. What it actually says
Verify Context
Check that:
CLAUDE.local.mdcontains required local facts..fcc/context/handoff.mdhas current state and next step..fcc/context/decisions.mdrecords durable decisions..mcp.jsonhas Token Savior as the baseline code retrieval server.- Only one persistent memory owner is active when persistent memory is enabled: MemSearch.
Report stale or conflicting context before editing code.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 12 lines · 0 tokens per session scan B 5c00dcac0490
verify-context is a command published in the GitHub repository sepehrbayat/SEPCC (38 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 90 tokens. A static security scan graded it B with 1 finding (reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
memstack-search
Search MemStack memory for past sessions, insights, and project context.
instinct-status
Show learned instincts (project + global) with confidence.
memory-why
Show why a memory recall returned what it did -- BM25 vs vector vs hybrid provenance.
context-stats
Display context window usage and token statistics.
memory-consent
Grant or revoke consent for session-end auto-memorize. Usage: /memory-consent yes|no|ask.
handoff
Create a handoff document for seamless session continuity.