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/piprail/piprail/releasegit clone --depth 1 https://github.com/piprail/piprailWhat 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.00022 | $0.00181 |
| Opus 5 | $0.00011 | $0.00090 |
| Sonnet 5 | $0.00004 | $0.00036 |
| Haiku 4.5 | $0.00002 | $0.00018 |
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 3d 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
Use the release skill at .claude/skills/release/SKILL.md as the playbook. Release: $ARGUMENTS
Non-negotiables (the skill expands each): run the verify-gate first; bump the version
in EVERY file (package.json + CHANGELOG.md, and for the MCP also server.json); commit
on main; then push a signed sdk-v* / mcp-v* tag — that's what publishes. Never
npm publish by hand. Build the SDK before the MCP. After CI publishes, create the GitHub
Release from the tag (and for the MCP, refresh the registry with mcp-publisher).
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.
- 3d ago First seen · 12 lines · 22 tokens per session scan A bff228ecabbb
release is a command published in the GitHub repository piprail/piprail (8 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 181 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.
Other commands, from other repositories
release
Cut an npm release of all 5 @t2000 packages via the GitHub Release workflow.
ship
Walk the ship checklist for a feature — surfaces, docs, and the catalog-from-live-truth rule.
OPSX: Archive
Archive a completed change in the experimental workflow.
review-renovate
Review and merge renovate PRs with automerge configuration updates.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
SHIP_RELEASE
Ship the active release/X.Y.Z — build the installer, merge to main, tag, push, and publish the GitHub release. Run after /prerelease passes.