Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add punt-labs/punt-kit/plugin install punt-devWrote 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-dev)<a href="https://agentmods.dev/commands/punt-labs/punt-kit/audit-dev"><img src="https://agentmods.dev/badge/commands/punt-labs/punt-kit/audit-dev/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-dev"><img src="https://agentmods.dev/badge/commands/punt-labs/punt-kit/audit-dev.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.00009 | $0.00232 |
| Opus 5.5 | $0.00004 | $0.00093 |
| Sonnet 5.5 | $0.00002 | $0.00046 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
audit-dev 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 26d 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 (Dev)
Run the compliance checker from the local working tree (not the installed CLI). Use this when developing punt-kit to test changes before publishing.
Input
Arguments: $ARGUMENTS (defaults to . if empty; pass --fix to auto-create missing mechanical files)
Process
Run in the user's current directory. ${CLAUDE_PLUGIN_ROOT} is punt-kit's
plugin/ subdirectory; --project selects its parent as the source project
without changing the current directory or the meaning of relative target paths.
uv run --project "${CLAUDE_PLUGIN_ROOT}/.." 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-dev:reconcile-dev.
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.
- 26d ago Changed b5d316ca7725
- 1mo ago First seen · 29 lines · 9 tokens per session scan A 58aa6579f2d5
audit-dev is a command published in the GitHub repository punt-labs/punt-kit (1 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 232 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
doctor-dev
Check Z specification environment health.
doctor
Check Z specification environment health.
build-fix
Systematically investigate and fix build errors, TypeScript errors, or test failures with minimal diffs.
partition-dev
Derive test cases from Z specification using TTF testing tactics.
data-flow-analysis
Trace how data flows through the system from input to output.
b-animate-dev
Animate and model-check a B machine with probcli.