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.
git clone --depth 1 https://github.com/appboypov/pew-pew-plaza-packsWrote 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/appboypov/pew-pew-plaza-packs/commit)<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/commit"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/commit/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/appboypov/pew-pew-plaza-packs/commit"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/commit.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.00012 | $0.00463 |
| Opus 5 | $0.00006 | $0.00231 |
| Sonnet 5 | $0.00002 | $0.00093 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
commit 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prompt Command
When this command is used, check if any required information is missing. If so, ask the user to provide it. Otherwise, proceed with the request.
🤖 Agent Command
When this command is used, adopt the following agent persona. You will introduce yourself once and then await the user's request.
Act as @agents/dev/git-expert.md and handle this commit operation following all project conventions.
Pre-Commit Documentation Review
Before committing, perform these essential documentation checks:
1. README.md Validation
Please read README.md with your Read tool:
- Ensure all information is up to date and accurate
- Add any missing features or capabilities
- Remove any outdated or invalid information
- Verify version badges and links are current
- Check that installation and usage instructions are correct
2. CHANGELOG.md Update
Please read CHANGELOG.md with your Read tool:
- Ensure the latest version section exists with proper formatting
- Add a new "## [Unreleased]" section at the top if none exists
- Update the current version section with any applicable changes from this commit:
-
💔 Breaking:
-
✨ Features:
-
🛠️ Improvements:
-
🐛 Bug fixes:
-
3. Additional Documentation Scan
Scan the project for any other relevant documentation that needs updates:
- Update any outdated documentation
- Add any missing documentation for new features
- Remove any invalid or deprecated documentation
- Ensure all references and links are working
Commit Options
After completing the documentation review and updates, proceed with:
- Commit Staged Changes: Commits only the files you have added to the staging area (
git add). This is for precise commits. I will rungit commit. - Commit All Changes: Stages all tracked and new files (
git add -A) and then commits them. This is to commit all your work at once. I will rungit add -Aand thengit commit.
If the user provided no preference, perform Commit All Changes.
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.
- 9d ago First seen · 58 lines · 12 tokens per session scan A 4ad44dc2564b
commit is a command published in the GitHub repository appboypov/pew-pew-plaza-packs (85 stars, last pushed 8mo ago), licensed MIT. It adds 12 tokens to every session and 463 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-09-03.
Other commands, from other repositories
commit-push-pr
An automated Git workflow that checks a project, synchronizes documentation, commits changes, and can create or merge a GitHub pull request. A pull request is a request for teammates to review and add changes to a shared codebase.
quick-commit
A quick Git command for committing and pushing a small code change. Git is the tool that records code versions and sends them to a shared repository.
plan-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
catchup
Restore context after /clear by summarizing recent work and project state.
commit
Generate a conventional commit message for staged changes.
changelog
Automatic changelog generation. Produces a structured changelog from commit history.