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/punt-labs/punt-kitWrote 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/punt-labs/punt-kit/audit)<a href="https://agentmods.dev/commands/punt-labs/punt-kit/audit"><img src="https://agentmods.dev/badge/commands/punt-labs/punt-kit/audit/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/punt-labs/punt-kit/audit"><img src="https://agentmods.dev/badge/commands/punt-labs/punt-kit/audit.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.00006 | $0.00142 |
| Opus 5.5 | $0.00002 | $0.00057 |
| Sonnet 5.5 | $0.00001 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
audit 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 1mo 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
Punt Audit
Run the deterministic compliance checker for a Punt Labs project.
Input
Arguments: $ARGUMENTS (defaults to . if empty; pass --fix to auto-create missing mechanical files)
Process
Run the audit command:
punt audit $ARGUMENTS
Report the output to the user. Summarize the pass/fail results.
If there are failures that --fix can resolve, suggest re-running with --fix. For issues requiring contextual judgment, suggest /punt reconcile.
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.
- 1mo ago First seen · 26 lines · 6 tokens per session scan A 36c54e7385f0
audit is a command published in the GitHub repository punt-labs/punt-kit (1 stars, last pushed yesterday), licensed MIT. It adds 6 tokens to every session and 142 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-31.
Other commands, from other repositories
feedback-to-us
Tell us how the prfaq plugin is working for you (anonymous 1-5 feedback).
badge
Generate a stage-colored badge and embed it in your README.
setup
Install and configure fuzz, probcli, and lean dependencies.
contracts-dev
Generate runtime contracts (preconditions, postconditions, invariants) from a Z specification.
code2model-dev
Create a Z specification for stateful entities in a system.
partition-dev
Derive test cases from Z specification using TTF testing tactics.