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/shipgit 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/ship)<a href="https://agentmods.dev/commands/nirelbaz/promptpit/ship"><img src="https://agentmods.dev/badge/commands/nirelbaz/promptpit/ship.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.00401 |
| Opus 5 | $0.00000 | $0.00200 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
ship 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 4d 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
Push the current branch and create a Pull Request. Run this after implementation is complete and tests pass.
Steps
-
Verify clean. Run
npm test && npm run lint && npm run build. All three must pass. If any fail, stop and fix them first. -
Check working tree. Run
git status. If there are uncommitted changes, ask the user whether to commit them (with a suggested message) or stash them. -
Push. Run
git push -u origin [branch-name]. If the branch already tracks a remote, justgit push. -
Create PR. Use
gh pr create:- Title: Under 70 chars, conventional commit prefix (
feat:,fix:,refactor:,test:,docs:). Extract from the primary commit message or the branch purpose. - Summary: 2-3 bullets extracted from
git log origin/main..HEAD --oneline. Describe what the user can now do, not implementation details. - Test plan: Extract test names from
git diff origin/main -- test/to build a checklist of what's covered.
Format:
gh pr create --title "[title]" --body "$(cat <<'EOF' ## Summary - [bullet from commits] - [bullet from commits] ## Test plan - [x] [test name from diff] - [x] [test name from diff] Generated with [Claude Code](https://claude.com/claude-code) EOF )" - Title: Under 70 chars, conventional commit prefix (
-
TODOS.md. Read TODOS.md. If this branch addresses any open items, suggest marking them complete using the project's existing format (strikethrough + completion note). Only modify TODOS.md if the user confirms.
-
Report. Print the PR URL.
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.
- 4d ago First seen · 35 lines · 0 tokens per session scan A e9da26226ebb
ship 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 401 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
bump-plugin
Bump changed plugin and marketplace version.
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.