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/github-release)<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/github-release"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/github-release/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/github-release"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/github-release.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.00025 | $0.01235 |
| Opus 5 | $0.00013 | $0.00617 |
| Sonnet 5 | $0.00005 | $0.00247 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade A, and why
create-github-release 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 — 172 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.
🚀 Create GitHub Release
Act as @agents/dev/git-expert.md and handle this complete GitHub release process following all project conventions.
Release Workflow
This prompt will guide you through the complete release process:
- Documentation Validation & Updates
- Changelog Version Management
- Version Validation & Tag Checking
- Commit Documentation Changes
- Create Git Tag
- Create GitHub Release
Phase 1: Documentation Validation & Updates
1.1 README.md Validation
Please read README.md with your Read tool and ensure:
- All information is up to date and accurate
- Version badges reflect the current release version
- Add any missing features or capabilities from recent changes
- Remove any outdated or invalid information
- Verify installation and usage instructions are correct
- Update any links or references that may have changed
- Ensure all command examples work with current version
1.2 Additional Documentation Scan
Scan the project for other relevant documentation and update as needed:
- Check for any outdated documentation
- Add missing documentation for new features
- Remove invalid or deprecated documentation
- Ensure all references and links are working
- Update any version-specific documentation
Phase 2: Changelog Version Management
2.1 Read Current Changelog
Please read CHANGELOG.md with your Read tool to understand the current state.
2.2 Version the Unreleased Section
- Convert the current
## [Unreleased]section to a proper version - Ask the user what version number to use (e.g., v0.7.0, v1.0.0, etc.)
- Format as:
## [v{VERSION}] - {YYYY-MM-DD}using today's date - Ensure all changes are properly categorized under:
-
💔 Breaking:
-
✨ Features:
-
🛠️ Improvements:
-
🐛 Bug fixes:
-
2.3 Create New Unreleased Section
- Add a new
## [Unreleased]section at the top for future changes - Leave it empty with just the header
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 · 172 lines · 25 tokens per session scan A 24c2828498ff
create-github-release is a command published in the GitHub repository appboypov/pew-pew-plaza-packs (85 stars, last pushed 8mo ago), licensed MIT. It adds 25 tokens to every session and 1,235 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
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
release-notes
Generate release notes in multiple formats from git commits.
ship
Comprehensive pre-deployment verification to ensure release readiness.
changelog
Automatic changelog generation. Produces a structured changelog from commit history.
release
Release notes command. Compiles changes into formats for 3 different audiences.
changelog-gen
CHANGELOG.md update command. Generates a changelog from git history grouped by conventional commit types.