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/closedloop-ai/claude-plugins/fixnpx skills add closedloop-ai/claude-plugins --skill fixgit clone --depth 1 https://github.com/closedloop-ai/claude-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.00027 | $0.04732 |
| Opus 5 | $0.00014 | $0.02366 |
| Sonnet 5 | $0.00005 | $0.00946 |
| Haiku 4.5 | $0.00003 | $0.00473 |
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.
How it starts
The opening of the file, as written. The whole thing — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Code Review Findings
Category-dispatch fix flow for findings from a prior code review. Each finding is routed to one of four buckets based on its category/subcategory: auto-fix, callsite-fix, specialized-fix, or manual-surface. Injection attempts, sensitive-file changes, and coverage gaps never auto-apply — they surface in a manual-action report instead.
The caller controls re-review cycles.
Arguments
$ARGUMENTS
Step 1: Parse Arguments and Load Findings
TodoWrite([
{"content": "Parse arguments and load findings", "status": "in_progress", "activeForm": "Parsing arguments"},
{"content": "Categorize findings and print dispatch plan", "status": "pending", "activeForm": "Categorizing findings"},
{"content": "Apply fixes per dispatch bucket", "status": "pending", "activeForm": "Applying fixes"},
{"content": "Print manual-action report", "status": "pending", "activeForm": "Printing manual-action report"},
{"content": "Run project verification", "status": "pending", "activeForm": "Running verification"},
{"content": "Print summary", "status": "pending", "activeForm": "Printing summary"}
])
Parse flags
Extract from $ARGUMENTS:
| Flag | Default | Effect |
|---|---|---|
<CR_DIR> (positional) |
auto-discover | Code-review session directory |
--include-medium |
off | Include MEDIUM findings (default: BLOCKING/HIGH only) |
--include-tentative |
off | Show TENTATIVE in manual-surface report (never auto-fixes) |
--include-justified |
off | Show JUSTIFIED-VALID in manual-surface report |
--dry-run |
off | Print dispatch plan and manual-action report; apply nothing |
--apply |
required in non-TTY | Required in non-interactive mode for code modification |
--category-only <name> |
unset | Restrict dispatch to a single category (e.g., --category-only Correctness) |
--skip-verification |
off | Skip the final code:build-validator step |
--dry-run and --apply are mutually exclusive. Both unset in non-interactive (no TTY) → print plan, exit without applying.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- templates/_generic.md 725 B
- templates/companion_change.md 1.1 KB
- templates/coverage_gap.md 1.3 KB
- templates/hygiene_sensitive.md 1011 B
- templates/impact_semantic_change.md 1.3 KB
- templates/injection_attempt.md 1.2 KB
- templates/pending_verification.md 1.8 KB
- templates/testquality_bug_locking.md 811 B
- templates/testquality_specialized.md 974 B
- templates/testquality_test_deletion.md 695 B
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 · 352 lines · 27 tokens per session scan A 117f71bc4ff3
fix is a skill published in the GitHub repository closedloop-ai/claude-plugins (103 stars, last pushed 4d ago), licensed Apache-2.0. It adds 27 tokens to every session and 4,732 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.
Other skills, from other repositories
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
evolve
Start or monitor an evolutionary development loop.
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.