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/geekatron/jerryWrote 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/geekatron/jerry/release)<a href="https://agentmods.dev/commands/geekatron/jerry/release"><img src="https://agentmods.dev/badge/commands/geekatron/jerry/release/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/geekatron/jerry/release"><img src="https://agentmods.dev/badge/commands/geekatron/jerry/release.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.00000 | $0.01214 |
| Opus 5.5 | $0.00000 | $0.00486 |
| Sonnet 5.5 | $0.00000 | $0.00243 |
| Haiku 4.5 | $0.00000 | $0.00121 |
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 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 219 lines · 0 tokens per session scan A 372f19f6153b
release is a command published in the GitHub repository geekatron/jerry (37 stars, last pushed 5d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 1,214 tokens. 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-30.
Other commands, from other repositories
release-check
Run the complete release readiness pipeline (version checks, changelog, final quality gates) and assign a release confidence score.
plan-release-train
Wraps agents/release-train-planner/AGENT.md. Produces package strategy, branching model, environment promotion path, release calendar, CI/CD gates, and hotfix playbook.
ship
Puts approved code into production and closes the cycle. PR + CI + deploy + simplify + docs + cleanup. Use after /fractal:review approves.
land
Resolve and squash merge one named, currently authorized pull request.
ship
Deploy feature through automated staging validation to production with rollback testing.
release-tag
Create and push a version tag after a release PR has been merged.