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-instinct-statusgit 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-instinct-status)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-instinct-status"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-instinct-status.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.00015 | $0.00371 |
| Opus 5 | $0.00008 | $0.00186 |
| Sonnet 5 | $0.00003 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
ccc-instinct-status 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
97% identical to instinct-status — 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
Instinct Status Command
Shows learned instincts for the current project plus global instincts, grouped by domain.
Implementation
Run the instinct CLI using the plugin root path:
python3 "${CLAUDE_PLUGIN_ROOT}/skills/continuous-learning-v2/scripts/instinct-cli.py" status
Or if CLAUDE_PLUGIN_ROOT is not set (manual installation), use:
python3 ~/.claude/skills/continuous-learning-v2/scripts/instinct-cli.py status
Usage
/instinct-status
What to Do
- Detect current project context (git remote/path hash)
- Read project instincts from
~/.claude/homunculus/projects/<project-id>/instincts/ - Read global instincts from
~/.claude/homunculus/instincts/ - Merge with precedence rules (project overrides global when IDs collide)
- Display grouped by domain with confidence bars and observation stats
Output Format
============================================================
INSTINCT STATUS - 12 total
============================================================
Project: my-app (a1b2c3d4e5f6)
Project instincts: 8
Global instincts: 4
## PROJECT-SCOPED (my-app)
### WORKFLOW (3)
███████░░░ 70% grep-before-edit [project]
trigger: when modifying code
## GLOBAL (apply to all projects)
### SECURITY (2)
█████████░ 85% validate-user-input [global]
trigger: when handling user input
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 · 60 lines · 15 tokens per session scan A a5214f9873bd
ccc-instinct-status is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 371 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to instinct-status, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
remember
Explicitly save something to memory as an experience.
evolution
Show what the system learned and changed recently.
rust-teach
One-time setup that scans your Rust project, understands its patterns and conventions, and writes a Rust-specific context section to your CLAUDE.md. Run once per project to establish persistent Rust guidelines.
trace
Use trace to save repo context, implementation notes, and package/file/branch memory.
codex-state
List saved Codex task state for the current workspace so a controller can resume the right thread.
broadcast
Run broadcast on a distilled Raw — update related existing pages conversationally.