Borrowing it
Nothing to install: this file belongs to panyam/mcpkit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/panyam/mcpkit/main/.claude/commands/example-audit.mdgit clone --depth 1 https://github.com/panyam/mcpkitWrote 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/panyam/mcpkit/example-audit)<a href="https://agentmods.dev/commands/panyam/mcpkit/example-audit"><img src="https://agentmods.dev/badge/commands/panyam/mcpkit/example-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/panyam/mcpkit/example-audit"><img src="https://agentmods.dev/badge/commands/panyam/mcpkit/example-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.00000 | $0.01023 |
| Opus 5.5 | $0.00000 | $0.00409 |
| Sonnet 5.5 | $0.00000 | $0.00205 |
| Haiku 4.5 | $0.00000 | $0.00102 |
Grade A, and why
example-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 2mo 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit an mcpkit example for compliance with examples/CONVENTIONS.md. Read-only — reports drift, never edits.
Args
$1— example name (e.g.discord-events) or relative path (e.g.examples/events/discord). If missing, ask.
Steps
-
Read
examples/CONVENTIONS.md. It is the spec; this skill is just the runner. If the doc has changed since this skill was written, follow the doc. -
Resolve the target directory:
- Try
examples/$1, thenexamples/events/$1, then treat$1as a relative path. - Refuse if the directory doesn't exist.
- Try
-
Detect example type — UI vs non-UI:
- UI: contains an
*.htmlfile ANDmain.gocallsserver.WithExtension(&ui.UIExtension{...}). Run the UI checklist (CONVENTIONS.md §8 second block). - Non-UI: everything else. Run the non-UI checklist (CONVENTIONS.md §8 first block).
- If ambiguous (e.g.
*.htmlpresent but no UI extension), report it as a finding and audit as non-UI.
- UI: contains an
-
Walk the checklist. For each item, attempt to verify automatically:
- File presence:
Read/LSthe path. - Code shape:
grepfor the canonical symbol or anti-pattern. - Doc shape: read the file and check section headers.
- Build precondition: run
cd <dir> && go build ./.... If it fails, emitbuild-brokenas the sole finding and skip checks that depend on a working build (especiallywalkthrough-md-fresh). - WALKTHROUGH.md drift: run
cd <dir> && go run . --doc mdand diff against the committed file.
- File presence:
-
Emit findings in the format under "## Output format" below. Use the canonical IDs from CONVENTIONS.md §8 (one per checklist item) so
/example-upgradecan match them deterministically. -
Do not edit any files. Do not run
just readme, do not rungo fmt, do not runjust tidy. The audit's only side effects are read operations + the--doc mdbuild attempt in step 4. -
Final line: print exactly
Audit complete: <N> pass, <M> failso a follow-up/example-upgradeinvocation can detect a recent audit in conversation context.
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.
- 2mo ago First seen · 77 lines · 0 tokens per session scan A 0c5d460fd6c4
example-audit is a command published in the GitHub repository panyam/mcpkit (6 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,023 tokens. 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
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
audio-pass
Functional audio review for implementation, mix coverage, clarity, and player feedback.
test-value-review
Use when a diff adds or changes test files, when a PR claims coverage for config, CI workflows, templates, or HTML output, or when tests look written only to satisfy a "must have tests" rule; not for Playwright selector or performance hygiene (use /playwright-review).
auditar-refactor
Invoca refactor-safety-auditor — gate canônico antes de qualquer refactor. Coleta evidências (linhas, contrato externo, coverage, mutation) e retorna veredito GO/BLOCK/WARN/GO-OVERRIDE.
quality-check-command
This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.