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/bonnguyenitc/specship/commit-push-prgit clone --depth 1 https://github.com/bonnguyenitc/specshipWhat 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.00013 | $0.00202 |
| Opus 5 | $0.00006 | $0.00101 |
| Sonnet 5 | $0.00003 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
commit-push-pr 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 2d 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
Commit the current changes, push, and open a pull request.
Pre-computed context:
- Branch: !
git branch --show-current - Status: !
git status --short - Diff: !
git diff --stat HEAD
Steps:
- Run
npm test. If it fails, stop and report — do not commit broken code. - If on
main, create a descriptive branch first (kebab-case, e.g.fix-merge-idempotency). - Stage and commit with a conventional message (
feat:,fix:,refactor:,docs:,test:) describing the why, not just the what. - Push with
git push -u origin <branch>. - Open a PR with
gh pr create— concise summary plus a test plan listing the verification you actually ran.
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.
- 2d ago First seen · 21 lines · 13 tokens per session scan A de0f4e3ad9b2
commit-push-pr is a command published in the GitHub repository bonnguyenitc/specship (2 stars, last pushed 24d ago), licensed MIT. It adds 13 tokens to every session and 202 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
roo-translate
Translate and localize strings in the CoStrict extension.
release
Create a new release of the CoStrict extension.
commit
Commit and push changes with a descriptive message.
roo-resolve-conflicts
Resolve merge conflicts intelligently using git history analysis.
status
Run Tau Git Memory status now.
git
Git operations with intelligent commit messages and workflow optimization.