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 skills add yu-iskw/coding-agent-fabric --skill build-and-fixgit clone --depth 1 https://github.com/yu-iskw/coding-agent-fabricWrote 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/skills/yu-iskw/coding-agent-fabric/build-and-fix)<a href="https://agentmods.dev/skills/yu-iskw/coding-agent-fabric/build-and-fix"><img src="https://agentmods.dev/badge/skills/yu-iskw/coding-agent-fabric/build-and-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/skills/yu-iskw/coding-agent-fabric/build-and-fix"><img src="https://agentmods.dev/badge/skills/yu-iskw/coding-agent-fabric/build-and-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.00043 | $0.00373 |
| Opus 5.5 | $0.00017 | $0.00149 |
| Sonnet 5.5 | $0.00009 | $0.00075 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
build-and-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
100% identical to build-and-fix — 0 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 Loop
Purpose
An autonomous loop for the agent to identify, analyze, and fix build errors using pnpm build.
Loop Logic
- Identify: Run
pnpm buildto identify build failures. - Analyze: Examine the build output to determine:
- The failing package and file.
- The specific compiler or build error message.
- Refer to ../common-references/troubleshooting.md for common TS errors.
- Fix: Apply the minimum necessary change to resolve the error (e.g., fixing TypeScript types, correcting imports, or updating configurations).
- Verify: Re-run
pnpm build.- If passed: Finish.
- If failed: Analyze the new failure and repeat the loop.
Termination Criteria
- The project builds successfully (as reported by
pnpm build). - Reached max iteration limit (default: 5).
- The error persists after multiple distinct fix attempts, indicating a need for human intervention.
Examples
Scenario: Fixing a TypeScript compilation error
pnpm buildfails because of a type mismatch inpackages/common/src/index.ts.- Agent analyzes the error and finds an incorrect interface implementation.
Resources
- pnpm Commands for Node.js: Common commands for building and managing dependencies.
- TypeScript Documentation: Official documentation for TypeScript.
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 · 41 lines · 43 tokens per session scan A f068a331b8f7
build-and-fix is a skill published in the GitHub repository yu-iskw/coding-agent-fabric (1 stars, last pushed 25d ago), licensed Apache-2.0. It adds 43 tokens to every session and 373 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to build-and-fix, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
firebase-crashlytics
Use when implementing crash reporting, capturing fatal/non-fatal errors, recording isolate/async exceptions, customizing reports, or uploading obfuscated symbols.
flutter-errors
Use when hitting layout errors (RenderFlex overflow, unbounded constraints, RenderBox not laid out), scroll errors, or setState-during-build errors.
code-context
How to answer codebase questions with the code-context MCP tools (search, sql, reindex): ranked hybrid keyword+semantic search, relevance-ranked SQL aggregation over the index, and index lifecycle. Use when a question spans many files ("how does X work", "where is Y handled"), when ranking or counting code by topic…
auto-service-technician
Use when a task needs senior auto-service-technician judgment — diagnosing a check-engine-light or drivability complaint from DTCs and live data, deciding whether a code-named part actually needs replacing or the fault lies upstream, scoping a flat-rate repair order and labor time, choosing warranty vs. customer-pay…
commercial-industrial-electronics-repairer
Use when a task needs the judgment of a Commercial and Industrial Electronics Repairer — diagnosing a VFD fault trip on a production line, tracing a PLC I/O fault back to the sensor, the wiring, or the ladder logic, selecting arc-flash PPE for live-panel diagnostic work, triaging multiple simultaneous down-lines by…
computer-user-support-specialist
Use when a task needs the judgment of a Computer User Support Specialist — triaging an inbound ticket's severity and SLA clock before troubleshooting it, verifying a caller's identity before any password/MFA/account-state change, walking a live incident through a structured troubleshooting sequence instead of guessing…