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.
npx agentmods add skills/zate/cc-plugins/fixnpx skills add Zate/cc-plugins --skill fixgit clone --depth 1 https://github.com/Zate/cc-pluginsWhat 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 | $0.00016 | $0.00512 |
| Opus 5 | $0.00008 | $0.00256 |
| Sonnet 5 | $0.00003 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
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 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.
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_POSITIVEfindings.
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.
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.
- 2d ago First seen · 69 lines · 16 tokens per session scan A 4cc329549451
fix is a skill published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 512 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…