audit

A command that reviews recent Git commits for possible defects, proves whether each finding is real, fixes confirmed problems, and verifies the affected parts of the software.

In plain words
What is it for?
Use it to audit a selected commit range, investigate value, concurrency, coverage, or type problems, and report findings as confirmed, dismissed, or no-op with evidence.
Why use it?
It reduces false bug reports and catches issues that a successful merge or green continuous-integration run may not reveal.

Command

Install

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.

agentmods
npx agentmods add commands/naimkatiman/continuous-improvement/audit
Clone the repo
git clone --depth 1 https://github.com/naimkatiman/continuous-improvement
Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 441 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00046 $0.00441
Opus 5 $0.00023 $0.00220
Sonnet 5 $0.00009 $0.00088
Haiku 4.5 $0.00005 $0.00044

Measured 3d ago against content hash c644266dc4ea, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 3d 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.

commands/audit.md · 35 lines

What it actually says

/audit — Confirm Recent Commits Before You Trust Them

Run the audit-driven loop over recent work: a merged commit with green CI is a claim, not a proof.

What it does

Takes a commit window, hunts for real defects one concern at a time, proves each finding against the actual code (false positives die before any edit), fixes on a branch with the smallest diff, verifies every surface the fix touches, and reports honestly. Backed by the audit skill.

The loop

1. Scope    git log to pick the window (e.g. HEAD~10..HEAD, or main since last release)
2. Find     one pass per dimension: value/economy drift, concurrency, surface coverage, type/contract
3. Confirm  read the actual lines; state in one sentence why it is real, or dismiss it
4. Fix      one concern per commit; prefer a failing test first, then green
5. Verify   exercise EVERY surface (backend, frontend, admin, cache, migration), not just the edited one
6. Report   confirmed (with the proof), dismissed (with why), no-op (in scope, nothing to change)

Default skeptical

Findings are hypotheses. Default each to a false positive until the code proves the bug — defaulting to "real" is how plausible-but-wrong fixes ship. For a thorough audit, fan the find pass out across dimensions with parallel reviewers, then verify each survivor adversarially.

Pairs with

  • audit skill — the discipline this command runs.
  • code-review / security-review — the per-dimension passes.
  • reconcile — the safe branch→PR path once the audit produces a fix.
  • recall — check whether a finding was already hit and fixed before.
Changes

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.

  1. 3d ago First seen · 35 lines · 46 tokens per session scan A c644266dc4ea

Subscribe to this mod's changes

audit is a command published in the GitHub repository naimkatiman/continuous-improvement (7 stars, last pushed 8d ago), licensed MIT. It adds 46 tokens to every session and 441 once invoked, about $0.0002 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-31.