plan

A preview command for cchad, a tool that proposes repository configuration changes. It shows which packages it would add and which it would skip, without changing the repository.

In plain words
What is it for?
Use it to review how cchad would configure the current repository, including each package's scope and reason for inclusion or exclusion.
Why use it?
It lets you inspect the proposed setup before applying anything. This avoids unexpected configuration changes.

Command

Install

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.

agentmods
npx agentmods add commands/cypsy1714/cchad/plan
Clone the repo
git clone --depth 1 https://github.com/Cypsy1714/cchad
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 95 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00014 $0.00095
Opus 5 $0.00007 $0.00048
Sonnet 5 $0.00003 $0.00019
Haiku 4.5 $0.00001 $0.00010

Measured yesterday against content hash 45af48a67842, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

plugins/cchad/commands/plan.md · 10 lines

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.

Changes

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.

  1. yesterday First seen · 10 lines · 14 tokens per session scan A 45af48a67842

Subscribe to this mod's changes

plan is a command published in the GitHub repository Cypsy1714/cchad (1 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 95 once invoked, about $0.0001 per session on Opus 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.