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.
git clone --depth 1 https://github.com/Cypsy1714/cchadWrote 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/cypsy1714/cchad/plan)<a href="https://agentmods.dev/commands/cypsy1714/cchad/plan"><img src="https://agentmods.dev/badge/commands/cypsy1714/cchad/plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/cypsy1714/cchad/plan"><img src="https://agentmods.dev/badge/commands/cypsy1714/cchad/plan.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00014 | $0.00095 |
| Opus 5.5 | $0.00006 | $0.00038 |
| Sonnet 5.5 | $0.00003 | $0.00019 |
| Haiku 4.5 | $0.00001 | $0.00010 |
Grade A, and why
plan 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 1mo 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.
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.
What it actually says
Run uvx cchad plan in the current working directory with the Bash tool and show
the user the resulting plan: the packages cchad would add (with scope and reason)
and the ones it would deliberately skip (with reason).
This is a preview only — do not apply anything. Mention they can run /cchad:init
to apply the plan.
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.
- 1mo ago First seen · 10 lines · 14 tokens per session scan A 45af48a67842
plan is a command published in the GitHub repository Cypsy1714/cchad (1 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 95 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
raw
Bypass Keyward detection for this single prompt — useful for discussing key formats, pasting example tokens, or sharing logs that contain dummy secrets.
key
Save an API key to /.claude/secrets/ .txt. The hook intercepts the value before it reaches the model.
recall-save
Generate / overwrite .recall/context.md with Recall's local offline summarizer.
notebook-query
Query the notebook knowledge base (SQLite) built by /agy:notebook — precise, grounded, cited. Ask in natural language ("sum the amounts by category", "which docs mention 'Acme Corp'", "build a project timeline") or pass raw SQL. Read-only. Use this when you need exact aggregates/lookups across a document corpus…
ccc-orchestrate
Run a sequential multi-agent workflow (feature, bugfix, refactor, security or custom chain) with structured handoffs, plus optional tmux and worktree workers for long-running sessions. Use when a task needs planner, implementer and reviewer stages in order.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.