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/nirelbaz/promptpit/releasegit clone --depth 1 https://github.com/nirelbaz/promptpitWrote 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/nirelbaz/promptpit/release)<a href="https://agentmods.dev/commands/nirelbaz/promptpit/release"><img src="https://agentmods.dev/badge/commands/nirelbaz/promptpit/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.00245 |
| Opus 5 | $0.00000 | $0.00122 |
| Sonnet 5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00024 |
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
Tag and publish the current main branch. Run this on main after merging a PR that includes a version bump.
Steps
-
Ensure we're on main. If not, stop and tell the user to switch to main first.
-
Ensure the working tree is clean. If there are uncommitted changes, stop.
-
Read the current version from
package.json. -
Check the tag doesn't already exist. Run
git tag -l vX.Y.Z. If it exists, stop and tell the user this version is already released. -
Verify CHANGELOG has an entry for this version. If not, stop and tell the user to run
/versionon their branch first. -
Run all checks. Run
npm test && npm run lint && npm run build. If anything fails, stop. -
Tag and push the tag:
git tag vX.Y.Z git push origin vX.Y.Z -
Confirm. Tell the user the tag is pushed and CI will now publish to npm and create a GitHub Release. Link to the Actions tab.
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 · 24 lines · 0 tokens per session scan A 02b0d295b54b
release is a command published in the GitHub repository nirelbaz/promptpit (6 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 245 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
release
You are performing a release for the mindkeg-mcp project. The user will provide the version as $ARGUMENTS (e.g., "0.2.0" or "patch" or "minor" or "major").
CHANGELOG
Command "CHANGELOG" from bytedance/UI-TARS-desktop, covering 0.4.0 2024-12-10 - add logging, 1.2.29, 1.2.28, 1.2.26 and 1.2.25.
ship
Deliver the increment. Then go live with a rollback you have run.
fix-layout
Command "fix-layout" from OpenRaiser/PaperFit, covering /fix-layout — 启动完整 vto 排版优化, 用户入口说明, 工具调用约定, 用法 and 直接执行入口.
release
Walk the llmwiki release process step by step.
show-status
作用: 显示当前 PaperFit 任务的运行状态、缺陷消除进度、视觉优先级、修复计划摘要和下一步行动；这是当前默认的“摘要 / 解释”入口。.