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/Maksim-Burtsev/punchcardWrote 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/maksim-burtsev/punchcard/pr)<a href="https://agentmods.dev/commands/maksim-burtsev/punchcard/pr"><img src="https://agentmods.dev/badge/commands/maksim-burtsev/punchcard/pr.svg" alt="Measured on agentmods" 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.00018 | $0.00175 |
| Opus 5 | $0.00009 | $0.00088 |
| Sonnet 5 | $0.00004 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
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 7d 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
Run the punchcard skill on the given target and post the result.
Target: $ARGUMENTS — a GitHub PR / GitLab MR URL, or a bare number resolved against the current repository's origin. No argument and no inferable PR for the current branch: say so and stop.
Perform the full punchcard review of that PR/MR exactly as the skill prescribes, then post it following the skill's "Posting to a PR/MR" section — including its interactive confirmation, its render mapping, and its degradation ladder when posting is not possible. The skill is the single source of truth; this command only names the target and the intent to post.
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.
- 7d ago First seen · 18 lines · 18 tokens per session scan A 3506e709c368
pr is a command published in the GitHub repository Maksim-Burtsev/punchcard (1 stars, last pushed 5d ago), licensed MIT. It adds 18 tokens to every session and 175 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
merge-check
A pre-merge checklist command for a GitHub pull request. A pull request is a proposed code change, and the command checks whether it meets the project’s documented requirements before merging.
release-kick
A release command for the River Review project that checks release instructions and pull-request state, updates an out-of-date branch, and verifies the release after merging.
plan-merge-order
A command that plans the order for merging several pull requests (PRs), which are proposed code changes reviewed before entering a shared branch. It checks their status and file changes, then studies dependencies and overlap to reduce rebasing work.
verify-agent-report
A command for checking whether an agent’s reported branch, pull request, commit, or files actually exist. A pull request is a proposed code change submitted for review.
pr
A command that drafts a pull request (PR) description, the summary attached to a code change for review, using a set template. It checks that the description matches the actual changes before finalizing it.
range-review
A read-only command for reviewing a range of Git changes, such as all pull requests merged for a release. It uses several review perspectives, checks findings against the source, and suggests how each finding should be handled.