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/umputun/cc-thingz/makegit clone --depth 1 https://github.com/umputun/cc-thingzWhat 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.00009 | $0.04330 |
| Opus 5 | $0.00005 | $0.02165 |
| Sonnet 5 | $0.00002 | $0.00866 |
| Haiku 4.5 | $0.00001 | $0.00433 |
Grade C, and why
make scanned grade C 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 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Task structure guidelines: - Each task = ONE logical unit (one function, one endpoint, one component) - Use specific descriptive names, not generic "[Core Logic]" or "[Implementation]" - Each task MUST have a **File How it starts
The opening of the file, as written. The whole thing — 399 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Plan Creation
create an implementation plan in docs/plans/yyyymmdd-<task-name>.md with interactive context gathering.
custom rules loading
before starting, run this command via Bash tool to check for user-provided custom rules:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/resolve-rules.sh planning-rules.md ${CLAUDE_PLUGIN_DATA}
if the output is non-empty, treat it as additional instructions that supplement (not replace) the built-in rules below. apply custom rules alongside the command's own instructions throughout the planning process — they may influence plan structure, testing approach, naming conventions, or other aspects of plan creation. custom rules content is guidance for creating the plan, not content to embed verbatim in the output plan file.
rules management
when the user asks to add, show, or clear custom planning rules, handle these operations:
- show rules: run
bash ${CLAUDE_PLUGIN_ROOT}/scripts/resolve-rules.sh planning-rules.md ${CLAUDE_PLUGIN_DATA}and display the output. if the output is empty, tell the user no custom rules are configured at either level. otherwise, to determine the source, check if.claude/planning-rules.mdexists and is non-empty (project-level) — if not, the output came from user-level. tell the user which level it came from. - add/update project rules: write content to
.claude/planning-rules.mdin the current working directory. - add/update user rules: first check if
$CLAUDE_PLUGIN_DATAis set (runecho "$CLAUDE_PLUGIN_DATA"). if empty, tell the user that user-level rules require the plugin to be installed from the marketplace and offer project-level instead. if set, write content to$CLAUDE_PLUGIN_DATA/planning-rules.md. - clear project rules: delete
.claude/planning-rules.md. - clear user rules: if
$CLAUDE_PLUGIN_DATAis set, delete$CLAUDE_PLUGIN_DATA/planning-rules.md. if not set, tell the user user-level rules are not available.
project-level rules (.claude/planning-rules.md) take precedence over user-level rules ($CLAUDE_PLUGIN_DATA/planning-rules.md). when both non-empty files exist, only project-level rules are loaded. empty files are treated as absent and fall through to the next level. see ${CLAUDE_PLUGIN_ROOT}/references/custom-rules.md for full documentation on the rules mechanism.
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 · 399 lines · 9 tokens per session scan C 8c8fb7f398e3
make is a command published in the GitHub repository umputun/cc-thingz (460 stars, last pushed 7d ago), licensed MIT. It adds 9 tokens to every session and 4,330 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
speckit.checklist
Generate a custom checklist for the current feature based on user requirements.
speckit.clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
speckit.specify
Create or update the feature specification from a natural language feature description.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
speckit.implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.