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/kevinzai/commander/ccc-projectsgit 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/commands/kevinzai/commander/ccc-projects)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-projects"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-projects.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.00011 | $0.00206 |
| Opus 5 | $0.00005 | $0.00103 |
| Sonnet 5 | $0.00002 | $0.00041 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
ccc-projects scanned grade A with 0 findings 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 yesterday.
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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
94% identical to projects — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Projects Command
List project registry entries and per-project instinct/observation counts for continuous-learning-v2.
Implementation
Run the instinct CLI using the plugin root path:
python3 "${CLAUDE_PLUGIN_ROOT}/skills/continuous-learning-v2/scripts/instinct-cli.py" projects
Or if CLAUDE_PLUGIN_ROOT is not set (manual installation):
python3 ~/.claude/skills/continuous-learning-v2/scripts/instinct-cli.py projects
Usage
/projects
What to Do
- Read
~/.claude/homunculus/projects.json - For each project, display:
- Project name, id, root, remote
- Personal and inherited instinct counts
- Observation event count
- Last seen timestamp
- Also display global instinct totals
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.
- yesterday First seen · 40 lines · 11 tokens per session scan A 746bcf0749f2
ccc-projects is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 206 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to projects, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
debug
Systematic debugging with hypotheses and evidence gathering.
review
Run a Codex code review of your working tree or a branch (read-only).
adv-codex
Send a prompt to Codex CLI and return the response.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
planning-triage
Quick-score an enhancement, bug, or feedback item using the impact-first triage framework. Creates an issue if approved.
add-hook
Add a new hook to .claude/settings.json. Quick operation, no full interview needed. Trigger phrases: "add hook", "auto-format on save", "run tests after edit", "lint on write", "run [command] after [tool]".