gsd:audit-fix

An automated workflow that finds issues, sorts them by severity, fixes selected findings, runs tests, and commits the changes.

In plain words
What is it for?
Use it to process audit findings, limit the number or severity of fixes, choose the audit source, preview classifications, and apply tested corrections.
Why use it?
It reduces the manual work of moving from an audit report to tested code changes. A dry-run option lets you review the findings and classifications before anything is fixed.

Command for Claude Code

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/kryptobaseddev/cleo/audit-fix
Clone the repo
git clone --depth 1 https://github.com/kryptobaseddev/cleo

Made for: Claude Code.

Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 294 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.00025 $0.00294
Opus 5 $0.00013 $0.00147
Sonnet 5 $0.00005 $0.00059
Haiku 4.5 $0.00003 $0.00029

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

Security

Grade A, and why

gsd:audit-fix 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 2d 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.

.cleo/agent-outputs/T-POMODORO-BENCH-2026-04-16/gsd/.claude/commands/gsd/audit-fix.md · 34 lines

What it actually says

Flags:

  • --max N — maximum findings to fix (default: 5)
  • --severity high|medium|all — minimum severity to process (default: medium)
  • --dry-run — classify findings without fixing (shows classification table)
  • --source <audit> — which audit to run (default: audit-uat)

<execution_context> @/tmp/pomodoro-bench/gsd/.claude/get-shit-done/workflows/audit-fix.md </execution_context>

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. 2d ago First seen · 34 lines · 25 tokens per session scan A 9c3bce563d87

Subscribe to this mod's changes

gsd:audit-fix is a command published in the GitHub repository kryptobaseddev/cleo (160 stars, last pushed 12d ago), licensed MIT. It adds 25 tokens to every session and 294 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.