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/stephengpope/thepopebot/commit-changesgit clone --depth 1 https://github.com/stephengpope/thepopebotWhat 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.00009 | $0.00340 |
| Opus 5 | $0.00005 | $0.00170 |
| Sonnet 5 | $0.00002 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
commit-changes 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
Create a git commit for all current changes. Follow these steps exactly:
Step 1 — Gather context
Run these in parallel:
git status(never use-uall)git diffandgit diff --cachedto see all staged and unstaged changesgit log --oneline -5to see recent commit message style
Step 2 — Stage everything
Run git add -A to stage ALL changes (tracked, untracked, deleted). Do NOT selectively stage files — always commit everything together. This overrides any default guidance about selective staging.
Step 3 — Write the commit message
Analyze ALL the changes and write a commit message that:
- Has a short summary line (under 72 chars) with a conventional prefix (
fix:,feat:,refactor:,chore:,docs:, etc.) - Leaves a blank line after the summary
- Includes a body that explains WHAT changed and WHY, grouped by area if there are multiple changes
- Is detailed but not excessive — hit the sweet spot between "fixed stuff" and a novel
Do NOT commit files that look like secrets (.env, credentials, tokens).
Step 4 — Commit
Use a HEREDOC for the message:
git commit -m "$(cat <<'EOF'
summary line here
Body here.
EOF
)"
Step 5 — Verify
Run git status to confirm the commit succeeded.
If there are $ARGUMENTS, use them as additional context for the commit message.
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 · 45 lines · 9 tokens per session scan A 57d648a91f06
commit-changes is a command published in the GitHub repository stephengpope/thepopebot (1,854 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 340 once invoked, about $0.0000 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.