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/Ashfaqbs/software-dev-ai-claude-toolkitWrote 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/ashfaqbs/software-dev-ai-claude-toolkit/build-fix)<a href="https://agentmods.dev/commands/ashfaqbs/software-dev-ai-claude-toolkit/build-fix"><img src="https://agentmods.dev/badge/commands/ashfaqbs/software-dev-ai-claude-toolkit/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/ashfaqbs/software-dev-ai-claude-toolkit/build-fix"><img src="https://agentmods.dev/badge/commands/ashfaqbs/software-dev-ai-claude-toolkit/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.00005 | $0.00195 |
| Opus 5.5 | $0.00002 | $0.00078 |
| Sonnet 5.5 | $0.00001 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00019 |
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.
What it actually says
Fix Build Errors
Process
- Run the project's build command:
- Java/Spring Boot:
./mvnw compileor./gradlew build - Python:
mypy .orpyright - JavaScript:
npm run buildornpx tsc --noEmit
- Java/Spring Boot:
- Parse the FIRST error only.
- Read the relevant file and fix that single error.
- Re-run the build.
- Repeat until build succeeds.
Rules
- Fix ONE error at a time. Don't try to fix everything at once.
- If a fix introduces new errors, revert and try a different approach.
- After 5 consecutive failures on the same error, stop and explain the root cause.
- Don't suppress warnings with
@SuppressWarnings,# type: ignore, or// @ts-ignoreunless there's no alternative.
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 · 23 lines · 5 tokens per session scan A 0a8582187de5
build-fix is a command published in the GitHub repository Ashfaqbs/software-dev-ai-claude-toolkit (27 stars, last pushed 1mo ago), licensed MIT. It adds 5 tokens to every session and 195 once invoked, about $0.0000 per session on Opus 5.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
review
Audit code in scope against architectural rules. Report drift findings with propose-confirm-commit per fix and a feedback loop to improve the rule corpus.
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
statusbar-doctor
Run cs doctor to diagnose why the status bar isn't showing what you expect.
trace-claude-code
Control Opik tracing for your Claude Code sessions.
doctor
Run read-only health checks on the Kobiton automate plugin (CLI, credentials, profile, vUSB client).
validate
Run SDLC compliance check against the current project. Validates build system, code quality, testing, CI/CD, security, documentation, VCS, and release configurations.