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/afaizalam2003/Master-claude-skillWrote 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/afaizalam2003/master-claude-skill/focused-fix)<a href="https://agentmods.dev/commands/afaizalam2003/master-claude-skill/focused-fix"><img src="https://agentmods.dev/badge/commands/afaizalam2003/master-claude-skill/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.00000 | $0.00233 |
| Opus 5 | $0.00000 | $0.00117 |
| Sonnet 5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $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 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.
This is a copy
100% identical to focused-fix — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 6d ago First seen · 18 lines · 0 tokens per session scan A a2fb1051ee92
focused-fix is a command published in the GitHub repository afaizalam2003/Master-claude-skill (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 233 tokens. A static security scan graded it A with 0 findings. It is 100% identical to focused-fix, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
debug
Systematic debugging: root cause before any fix, one hypothesis at a time, and a three-strikes rule that questions the architecture instead of stacking patches.
doctor
Run read-only health checks on the Kobiton automate plugin (CLI, credentials, profile).
validate
Run SDLC compliance check against the current project. Validates build system, code quality, testing, CI/CD, security, documentation, VCS, and release configurations.
Diagnose
Run a 20-point health check across the plugin install, project config, PM/notification reachability, docs freshness, board consistency, and git state. Read-only — never changes state. Reports each check as PASS/WARN/FAIL/SKIP with an actionable fix. Target under 15 seconds end-to-end. Use before demos, after a plugin…
trace
Export a Grok session trace locally, or upload it to xAI.
review
You are a helpful coding expert. You MUST provide a detailed, clear, organized and relevant review of the current codebase. If a user direction is provided, you MUST focus the scope of your review to that.