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/MCKRUZ/claude-code-masteryWrote 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/mckruz/claude-code-mastery/build-fix)<a href="https://agentmods.dev/commands/mckruz/claude-code-mastery/build-fix"><img src="https://agentmods.dev/badge/commands/mckruz/claude-code-mastery/build-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.
<a href="https://agentmods.dev/commands/mckruz/claude-code-mastery/build-fix"><img src="https://agentmods.dev/badge/commands/mckruz/claude-code-mastery/build-fix.svg" alt="Reviewed on agentmods" width="80" 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.00024 | $0.00219 |
| Opus 5.5 | $0.00010 | $0.00088 |
| Sonnet 5.5 | $0.00005 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
/build-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.
This is a copy
83% identical to build-fix — 24 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
Build and Fix
Incrementally fix TypeScript and build errors with verification after each fix.
Workflow
-
Run build:
npm run buildorpnpm build -
Parse error output:
- Group by file
- Sort by severity
-
For each error:
- Show error context (5 lines before/after)
- Explain the issue
- Propose fix
- Apply fix
- Re-run build
- Verify error resolved
-
Stop if:
- Fix introduces new errors
- Same error persists after 3 attempts
- User requests pause
-
Show summary:
- Errors fixed
- Errors remaining
- New errors introduced
Important
Fix one error at a time for safety. Always verify the build after each fix before moving to the next error.
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 · 39 lines · 24 tokens per session scan A 82c964e5c3c7
/build-fix is a command published in the GitHub repository MCKRUZ/claude-code-mastery (11 stars, last pushed 6mo ago), licensed MIT. It adds 24 tokens to every session and 219 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 83% identical to build-fix, differing in 24 lines, and is treated as a copy.
Other commands, from other repositories
build-fix
Systematically diagnose and fix build errors, type errors, or failing CI.
types
Debug and fix TypeScript type errors with systematic analysis and expert guidance.
skill-mcp-server
Padrões DARE para servidores MCP (Model Context Protocol) em TypeScript ou Python. Tools, resources, prompts; transports stdio/SSE/HTTP; validação Zod/Pydantic; autorização por tool; tracing; testes; publicação.
skill-nestjs-api
Padrões DARE para APIs REST em NestJS + TypeScript + Prisma + Swagger. Modules, Controllers, Services, DTOs com class-validator, Guards JWT, throttler, exceções globais, Jest + Supertest, OpenAPI auto-gerado.
build-fix
Fix build and TypeScript errors with minimal changes.
build-fix
Incrementally fix TypeScript and build errors with minimal diffs. Fix one error at a time for safety.