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/jayminwest/canopy/releasegit clone --depth 1 https://github.com/jayminwest/canopyWhat 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.00001 | $0.00277 |
| Opus 5 | $0.00000 | $0.00138 |
| Sonnet 5 | $0.00000 | $0.00055 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
release 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
86% identical to release — 6 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
body
Analyze all changes since the last release and prepare a new version.
Steps:
- Find the last release tag:
git describe --tags --abbrev=0 2>/dev/null || echo "none" - If there's a previous tag, review changes:
git log <tag>..HEAD --onelineandgit diff <tag>..HEAD - Determine the version bump level. Always use patch unless the user explicitly requests minor or major.
- Bump version in both
package.jsonandsrc/index.tsusingbun run version:bump <level> - Update
CHANGELOG.md— move items from [Unreleased] to the new version section with today's date - Update
CLAUDE.mdif command counts or structure changed - Update
README.md:- Update test count and file count in the Development section (run
bun testto get current numbers) - Update CLI reference tables if commands were added, removed, or had flags changed
- Update command count in Project Structure section if commands were added or removed
- Update any other stats or structural information that changed
- Update test count and file count in the Development section (run
- Commit all changes with a message like "release: vX.Y.Z". Then present a summary of what changed.
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 · 23 lines · 1 tokens per session scan A 3fa8a4875fa0
release is a command published in the GitHub repository jayminwest/canopy (39 stars, last pushed 28d ago), licensed MIT. It adds 1 tokens to every session and 277 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to release, differing in 6 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
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.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.