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 skills/kevinzai/commander/ccc-recallnpx skills add KevinZai/commander --skill ccc-recallgit clone --depth 1 https://github.com/KevinZai/commanderWrote 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/skills/kevinzai/commander/ccc-recall)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-recall"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-recall.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.00036 | $0.01003 |
| Opus 5 | $0.00018 | $0.00502 |
| Sonnet 5 | $0.00007 | $0.00201 |
| Haiku 4.5 | $0.00004 | $0.00100 |
Grade B, and why
ccc-recall 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 agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -l "${keyword}" ~/.claude/sessions/*.tmp | head -5 How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-recall — Cross-Session Memory Search
Your past sessions are a goldmine. This skill indexes it.
Optional integration: If you have
claude-mem(a separate AGPL-licensed tool by @thedotmack) installed vianpm install claude-mem,$ccc-recallwill use it for vector search across sessions. CC Commander does NOT bundle claude-mem — install separately or skip; CCC's built-in grep + file-based recall works without it.
When to use
- "Didn't we solve this last month?" — search instead of re-solving
- "What did I decide about {auth provider / db vendor / testing lib}?" — pull the decision
- "When did {bug} first appear?" — find the session it landed in
- "Which file had that specific comment about the edge case?" — grep across sessions
Not for
- Current session state — that's
$ccc-memory(curated) or$ccc-save-session(snapshot) - Code search across the repo — use
Greptool directly - Documentation lookup — use
context7MCP or$ccc-docs
Three-layer lookup
Run them in order of fastest-first:
Layer 1 — Session transcripts (~/.claude/sessions/*.tmp)
File-based. Fast grep:
grep -l "${keyword}" ~/.claude/sessions/*.tmp | head -5
Returns session files whose summary mentions the keyword. Each is a structured save from $ccc-save-session with sections for What Worked / Didn't Work / Decisions.
Layer 2 — memory/ curated notes
If project has a memory/ dir (from $ccc-memory):
grep -rn "${keyword}" memory/
Higher signal than transcripts — you curated these specifically because they mattered.
Layer 3 — Full-text search across all sessions
If you need deeper semantic matches beyond Layer 1-2, search the full session corpus with glob:
grep -rn "${keyword}" ~/.claude/sessions/ --include="*.tmp" --include="*.md"
This indexes all session transcripts and archived notes. Best for semantic matches ("the time we debated SSE vs WebSocket") vs literal keyword, using native grep with context flags.
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 · 90 lines · 36 tokens per session scan B 1634889e263e
ccc-recall is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 1,003 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
codify-lesson
Detect recurring P2/P3 audit patterns across recent rounds and promote them into lesson cards. Use after round boundaries or when repeated findings appear.
cross-session-handoff
Read, write, snapshot, and lock .arcgentic/state.yaml across planner, dev, audit, and optional test sessions.
evolving-status
View Self-Evolving Loop session status, history, and memory metrics.
system-boot
Auto-activating session startup - reads memory, orients Claude, announces status. Triggers on session start or when user says "continue", "weiter", "resume".
performance-audit
Full-stack performance health check across 12 dimensions. Rendering, bundles, assets, API/network, algorithms, memory, database, caching, Web Vitals, backend runtime, concurrency, and framework-specific pathologies. Evidence-based Impact Models with confidence tiers and a prioritized optimization roadmap. Switches…
setup-memory
Configure project memory: write CLAUDE.md with architecture context and (Tier 3) set up a self-sustaining .claude/memory/ lifecycle — SessionStart load hook, Stop save-nudge hook, and a /save-memory skill that distills each session. Called by init or standalone to configure the memory pillar. Trigger phrases: "setup…