A command that applies a code change for one confirmed security finding identified by its ID. It changes the repository only when the finding is validated and has not already been addressed.

Use it to fix a specific finding such as F-001 after a web or mobile security scan.

It lets you target one known problem without rerunning or fixing unrelated findings.

fix-issue — Command for Claude Code by tinoimammp: A command that applies a code change for one…

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add tinoimammp/vantage-security-agent

Claude Code

/plugin install vantage

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-issue.svg)](https://agentmods.dev/commands/tinoimammp/vantage-security-agent/fix-issue)

Your own site

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

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

When invoked 454 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.00027	$0.00454
Opus 5	$0.00014	$0.00227
Sonnet 5	$0.00005	$0.00091
Haiku 4.5	$0.00003	$0.00045

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

Security

Grade A, and why

fix-issue 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 6d 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-issue.md · 36 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 finding $ARGUMENTS (a finding id like F-001) against the current project.

If no id was given, stop and ask for one — do not guess which finding to fix.
Read ./.vantage/artifacts/findings/validated-findings.json. Find the entry with this id.
- Not found → stop, report that the id doesn't exist (maybe check spelling, or run /vantage:scan-web//vantage:scan-mobile first).
- Found but validated: false → stop, report that only validated findings can be fixed.
- ./.vantage/artifacts/fixes/<id>.md already exists → stop, report it's already been addressed (fixed or marked not_auto_fixable) — don't re-apply.
Dispatch fix-agent via Task for this one finding. It reads its own methodology from ${CLAUDE_PLUGIN_ROOT}/agents/others/fix-agent.md, re-locates the vulnerable pattern in the current source (it may have moved), and applies the minimal targeted edit implementing the remediation — or marks it not_auto_fixable with a reason if a safe automated edit isn't possible.
Confirm ./.vantage/artifacts/fixes/<id>.md was written, and append the result to ./.vantage/artifacts/run-log.md.

Report which file(s) changed (or why the fix was skipped), and remind the user that fix-agent never runs a build or test suite — they must review the 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.

6d ago First seen · 36 lines · 27 tokens per session scan A 45c36f6cb58e

Subscribe to this mod's changes

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

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

mobile-audit

propagate

sinks