A command for fixing one security finding from the latest scan report. It selects a suitable fix guide based on the finding's weakness category, such as injection, authentication, cryptography, or configuration.

Loading a finding by ID or location, checking whether it is a real issue, inspecting the affected code, routing it to the right remediation guide, and applying or explaining the fix.

It connects a reported issue to the relevant remediation steps instead of requiring the developer to choose a fix approach manually.

fix — Skill for Claude Code by Zate/cc-plugins

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.

Any agent

npx skills add Zate/cc-plugins --skill fix

Clone the repo

git clone --depth 1 https://github.com/Zate/cc-plugins

Made for: Claude Code.

Or install security, the plugin that ships this one along with the rest of its 6 skills, 1 agent.

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/skills/zate/cc-plugins/fix/github.svg)](https://agentmods.dev/skills/zate/cc-plugins/fix)

Your own site

<a href="https://agentmods.dev/skills/zate/cc-plugins/fix"><img src="https://agentmods.dev/badge/skills/zate/cc-plugins/fix/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/zate/cc-plugins/fix"><img src="https://agentmods.dev/badge/skills/zate/cc-plugins/fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 512 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.00016	$0.00512
Opus 5.5	$0.00006	$0.00205
Sonnet 5.5	$0.00003	$0.00102
Haiku 4.5	$0.00002	$0.00051

Measured 1mo ago against content hash 4cc329549451, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

plugins/security/skills/fix/SKILL.md · 69 lines

What it actually says

Security Fix

Remediate one finding from .security/triaged.json or .security/report.md.

Step 1: Load Finding

Read .security/triaged.json. If it does not exist, tell the user to run /security:scan first.

Resolve $ARGUMENTS as:

exact finding ID, e.g. finding-003
CWE plus file/line, e.g. CWE-89 src/db.py:42
if omitted, ask the user to select from CRITICAL/HIGH TRUE_POSITIVE findings.

If the finding verdict is FALSE_POSITIVE, stop and suggest suppressing it with /security:scan --suppress <id>.

Step 2: Load Remediation Skill

Route by CWE/category:

CWE/category	Skill
CWE-78, CWE-79, CWE-89, injection, XSS	`remediation-injection`
CWE-798, CWE-287, CWE-502, auth, authorization, deserialization	`remediation-auth`
CWE-327, CWE-330, TLS, crypto, randomness	`remediation-crypto`
CWE-22, CWE-489, headers, deployment, config	`remediation-config`
Other	`remediation-library`

Use the selected remediation skill for the fix pattern.

Step 3: Inspect Minimal Context

Read the affected file around the finding and only nearby helper code needed to make a safe edit. Do not broaden into unrelated security work.

Step 4: Fix or Dry Run

If --dry-run is present, report the proposed change without editing.

Otherwise:

Apply the minimal secure change.
Preserve existing behavior.
Add or adjust focused tests only when the project already has a clear test pattern.
Run the narrowest relevant verification command available.

Step 5: Update User

Report:

Finding fixed.
File changed.
Verification run.
Recommended follow-up: /security:scan --diff.

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.

1mo ago First seen · 69 lines · 16 tokens per session scan A 4cc329549451

Subscribe to this mod's changes

fix is a skill published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 512 once invoked, about $0.0001 per session on Opus 5.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

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.