claude-skills is a large collection of reusable skills, commands, plugins, and supporting resources for coding agents across engineering, business, research, compliance, and productivity work. It is used by people who want agents such as Claude Code, Codex, Gemini CLI, or Cursor to follow specialized workflows. The catalogue contains selected skills and settings from the collection.
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.
git clone --depth 1 https://github.com/alirezarezvani/claude-skillsWrote 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.
[](https://agentmods.dev/commands/alirezarezvani/claude-skills/focused-fix)<a href="https://agentmods.dev/commands/alirezarezvani/claude-skills/focused-fix"><img src="https://agentmods.dev/badge/commands/alirezarezvani/claude-skills/focused-fix.svg" alt="Measured on agentmods" height="20"></a>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.00023 | $0.00234 |
| Opus 5 | $0.00012 | $0.00117 |
| Sonnet 5 | $0.00005 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
focused-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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- focused-fix — 100% identical, 2 lines differ
What it actually says
Systematically repair the feature/module at $ARGUMENTS using the focused-fix 5-phase protocol.
If $ARGUMENTS is empty, ask which feature/module to fix.
Read engineering/focused-fix/SKILL.md and execute ALL 5 phases IN ORDER:
- SCOPE — Map the feature boundary (all files, entry points, internal files)
- TRACE — Map inbound + outbound dependencies across the entire codebase
- DIAGNOSE — Check code, runtime, tests, logs, config. Assign risk labels (HIGH/MED/LOW). Confirm root causes with evidence.
- FIX — Repair in order: deps → types → logic → tests → integration. One fix at a time, test after each. 3-strike escalation if fixes cascade.
- VERIFY — Run all feature tests + consumer tests. Summarize changes.
Iron Law: No fixes before completing Phase 3. No exceptions.
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.
- 8d ago First seen · 18 lines · 23 tokens per session scan A 382d54f8cd28
focused-fix is a command published in the GitHub repository alirezarezvani/claude-skills (25,635 stars, last pushed 8d ago), licensed MIT. It adds 23 tokens to every session and 234 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 commands, from other repositories
doctor
Check OCR installation and verify all dependencies are available.
backprop
Trace a bug back to a spec gap and generate regression tests.
work-flow-bugfix
Complete workflow to fix a bug, from diagnosis to deployment.
dev-debug
Methodical and systematic bug diagnostic and resolution.
dev-error-handling
Implements a robust and consistent error handling strategy.
ops-ci-fix
Diagnose and repair failing CI/CD pipelines.