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/brief)<a href="https://agentmods.dev/commands/maksim-burtsev/punchcard/brief"><img src="https://agentmods.dev/badge/commands/maksim-burtsev/punchcard/brief/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/maksim-burtsev/punchcard/brief"><img src="https://agentmods.dev/badge/commands/maksim-burtsev/punchcard/brief.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.00024 | $0.00304 |
| Opus 5 | $0.00012 | $0.00152 |
| Sonnet 5 | $0.00005 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
brief 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 5d 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 brief on the given target.
Target: $ARGUMENTS — a GitHub PR / GitLab MR URL, or a branch or range in the current repository. No argument: the current branch against the repository's default branch. Standing on the default branch with no argument there is nothing to brief, and the brief says exactly that in one line and stops.
Write the brief of that change exactly as skills/punchcard/BRIEF.md
prescribes — it lives next to the punchcard skill — including its four
sections, its grounded map, its rule that nothing is cut to fit, and its
ban on findings. The brief renders in the conversation and is never
posted into the PR/MR. BRIEF.md is the single source of truth; this
command only names the target.
Two things about the reply itself. The user's own words around this command set the language of the brief: a user who wrote their message in Russian gets the brief in Russian, whatever language this command, the skill file, the diff and the description are in; only the four section titles stay in English. And the reply is the brief alone, starting at its bold header line — no sentence before it about being ready to write it.
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.
- 5d ago First seen · 27 lines · 24 tokens per session scan A 627a8953ad86
brief is a command published in the GitHub repository Maksim-Burtsev/punchcard (1 stars, last pushed 6d ago), licensed MIT. It adds 24 tokens to every session and 304 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-04.
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.
spec-release
Generate release notes, changelog, and deployment checklist.