The Pope Bot is an app for configuring an autonomous AI agent that can chat, run coding work, and operate continuously through connected language models and coding agents. People use it for questions, code changes, background development jobs, and live browser-based coding sessions. Its catalogue add-ons extend the bot with commands, skills, and operating instructions.
Borrowing it
Nothing to install: this file belongs to stephengpope/thepopebot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/stephengpope/thepopebot/main/.claude/commands/commit-changes.mdgit clone --depth 1 https://github.com/stephengpope/thepopebotWrote 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/stephengpope/thepopebot/commit-changes)<a href="https://agentmods.dev/commands/stephengpope/thepopebot/commit-changes"><img src="https://agentmods.dev/badge/commands/stephengpope/thepopebot/commit-changes/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/stephengpope/thepopebot/commit-changes"><img src="https://agentmods.dev/badge/commands/stephengpope/thepopebot/commit-changes.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00009 | $0.00340 |
| Opus 5.5 | $0.00004 | $0.00136 |
| Sonnet 5.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 2mo 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.
- 2mo 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,857 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 340 once invoked, about $0.0000 per session on Opus 5.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
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.
step6-ship
Pipeline Step 6 — Ship the completed phase: commit, update roadmap, capture postmortem, optionally push and create PR.