A command that applies code changes for every security problem already confirmed in the repository. It handles findings one at a time and records the result.

Use it after a security scan has produced validated findings, then review the resulting code changes before committing them.

It removes the need to manually apply each approved security fix and avoids changing the same files concurrently.

fix — Command for Claude Code by tinoimammp: A command that applies code changes for every security…

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/tinoimammp/vantage-security-agent/fix

Clone the repo

git clone --depth 1 https://github.com/tinoimammp/vantage-security-agent

Made for: Claude Code.

Or install vantage, the plugin that ships this one along with the rest of its 1 skill, 6 commands.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/tinoimammp/vantage-security-agent/fix.svg)](https://agentmods.dev/commands/tinoimammp/vantage-security-agent/fix)

Your own site

<a href="https://agentmods.dev/commands/tinoimammp/vantage-security-agent/fix"><img src="https://agentmods.dev/badge/commands/tinoimammp/vantage-security-agent/fix.svg" alt="Measured on agentmods" height="20"></a>

Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 413 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.

Model	Per session	Once invoked
Fable 5.1	$0.00021	$0.00413
Opus 5	$0.00010	$0.00206
Sonnet 5	$0.00004	$0.00083
Haiku 4.5	$0.00002	$0.00041

Measured 5d ago against content hash 01d1779d09dc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

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 5d 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/fix.md · 33 lines

What it actually says

This command modifies source code in the current repository. Unlike every scan command, this is destructive by design — review the result with git diff before committing.

Fix every validated finding against $ARGUMENTS (default: current working directory).

Read ./.vantage/artifacts/findings/validated-findings.json. Build the list of validated[] entries that do not already have a ./.vantage/artifacts/fixes/<id>.md record.
- If there are none (no validated findings, or all already have a fix record), say so and stop — do not fabricate work.
Sort the remaining list by severity: Critical → High → Medium → Low → Info.
Dispatch fix-agent via Task sequentially, one finding at a time — never in parallel. Multiple fixes may touch the same file, and concurrent edits to one file would corrupt it; process the list one Task call at a time, waiting for each to finish (and its artifacts/fixes/<id>.md to be written) before starting the next.
If one finding is not_auto_fixable, log it and continue to the next — don't stop the whole batch for one skip.
Append each result to ./.vantage/artifacts/run-log.md.

When done, report a summary table: how many fixed, how many not_auto_fixable (with reasons), and which files were touched overall. Remind the user that fix-agent never runs a build or test suite — they must review the diff (git diff) and run their own tests before committing.

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.

5d ago First seen · 33 lines · 21 tokens per session scan A 01d1779d09dc

Subscribe to this mod's changes

fix is a command published in the GitHub repository tinoimammp/vantage-security-agent (4 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 413 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-31.

Security ai-agents appsec mobile-security owasp sast security-tools

fix

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

review-cheatsheet-pr

scope

threats

propagate

sinks

trace