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/irskep/persistproc/releasegit clone --depth 1 https://github.com/irskep/persistprocWrote 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/irskep/persistproc/release)<a href="https://agentmods.dev/commands/irskep/persistproc/release"><img src="https://agentmods.dev/badge/commands/irskep/persistproc/release.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00067 |
| Opus 5 | $0.00000 | $0.00034 |
| Sonnet 5 | $0.00000 | $0.00013 |
| Haiku 4.5 | $0.00000 | $0.00007 |
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
- Make a vx.y.z tag for the next release based on CHANGELOG.md and push it to origin.
- Use pbcopy to copy the relevant release notes from CHANGELOG.md to the clipboard.
- Bump the patch version, commit, and push that to main, updating CHANGELOG.md with the new section.
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 · 4 lines · 0 tokens per session scan A 7d2209f3b235
release is a command published in the GitHub repository irskep/persistproc (8 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 67 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-31.
Other commands, from other repositories
review-renovate
Review and merge renovate PRs with automerge configuration updates.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
release
Ship a stable cmux release built by CI: bump version, update changelog, open a PR, merge, tag, then GitHub Actions builds, signs, and publishes.
merge-and-status
Merge the current PR, pull main, surface any open contributor PRs and untriaged contributor issues, and show open milestone issues.
release
Prepare a release by updating docs and bumping the version.