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.
npx agentmods add commands/iliaal/whetstone/audit-plugingit clone --depth 1 https://github.com/iliaal/whetstoneWrote 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/iliaal/whetstone/audit-plugin)<a href="https://agentmods.dev/commands/iliaal/whetstone/audit-plugin"><img src="https://agentmods.dev/badge/commands/iliaal/whetstone/audit-plugin.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 | $0.00025 | $0.05442 |
| Opus 5 | $0.00013 | $0.02721 |
| Sonnet 5 | $0.00005 | $0.01088 |
| Haiku 4.5 | $0.00003 | $0.00544 |
Grade A, and why
audit-plugin 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 4d 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit plugin content
Deep analysis of all skills, agents, and commands in the whetstone plugin. Surfaces quality issues that degrade skill effectiveness, waste tokens, or confuse the model.
Scope
PLUGIN_DIR=plugins/whetstone
SYNC_LOG=docs/audit/audit-log.md
If $ARGUMENTS specifies a name or category, narrow to that. Otherwise audit everything. Normalize component names to the ia- prefix before using them as --skill/--component filters (e.g. debugging → ia-debugging). Exit code 2 from those commands means the filter matched nothing — almost always a missing prefix — not a validation failure; re-run with the prefixed name.
Reactive mode: If invoked after a skill/agent failed during use, detect the failing component from conversation context and focus the audit on that component first.
Phase 0: Pre-flight — read prior decision log
Read $SYNC_LOG in full before any checks run. Build an in-memory set of already-evaluated findings keyed by (component, issue-signature) across every run entry. Use it as a filter during Phase 3 presentation:
- Previously applied, exact match — drop silently.
- Previously rejected, exact match — drop silently unless new evidence contradicts the prior reason; if so, surface with a
RE-EVALUATEflag and quote the prior rejection reason. - Previously deferred, exact match — surface with a
PREVIOUSLY DEFERREDtag and the original defer reason so the user can judge whether conditions have changed. - No match — present normally.
While reading, also detect prune triggers and emit a one-line reminder at the end of Phase 3 if any fire:
- Any entry older than 30 days.
- Any entry referencing a component that no longer exists under
$PLUGIN_DIR. - Any entry whose reasoning has been superseded by a feedback-memory rule.
Reminder format: "Sync log has N prune candidates — run /prune-sync-log."
If $SYNC_LOG doesn't exist, note it and continue — the post-apply step in Phase 5b creates 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.
- 4d ago First seen · 318 lines · 25 tokens per session scan A ee2b7a8d78bd
audit-plugin is a command published in the GitHub repository iliaal/whetstone (32 stars, last pushed 5d ago), licensed MIT. It adds 25 tokens to every session and 5,442 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-30.
Other commands, from other repositories
composite-actions
Generate, review, secure, and test composite GitHub Actions following best practices — full repo scaffold, interview-driven generation, PR creation on existing repos, SHA pinning, secrets-as-inputs, job summaries, and actionlint validation.
github-actions
Design, review, secure, and debug GitHub Actions workflows — reusable workflows, OIDC federation, SHA pinning, token scoping, promotion orchestration, and CI failure diagnosis.
datadog
Set up and troubleshoot Datadog — Agent deployment on Kubernetes, APM instrumentation, Log Management, Monitors, Dashboards, SLOs, Synthetic tests, and live incident investigation using the Datadog MCP server. Covers Terraform-managed Datadog resources.
fluxcd
FluxCD entry point — routes to the right workflow based on what you need. Live cluster issue → structured 5-workflow debug trace. Repo health check → 6-phase audit (discovery, validation, API compliance, best practices, security). Helm chart review → helmchart. Starts by asking one question to confirm the right mode.
linkerd
Linkerd-specific diagnostics — mTLS verification, proxy injection issues, authorization policy debugging, traffic management, and multi-cluster connectivity problems.
terraform
Runs through the full Terraform validation pipeline — fmt, validate, tflint, security scan — and reviews a module or plan for blast radius, IAM risk, and state impact.