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 agentmods add agents/obsidian-owl/specwright/specwright-build-fixergit clone --depth 1 https://github.com/Obsidian-Owl/specwrightWrote 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/agents/obsidian-owl/specwright/specwright-build-fixer)<a href="https://agentmods.dev/agents/obsidian-owl/specwright/specwright-build-fixer"><img src="https://agentmods.dev/badge/agents/obsidian-owl/specwright/specwright-build-fixer.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 | $0.00028 | $0.00455 |
| Opus 5 | $0.00014 | $0.00228 |
| Sonnet 5 | $0.00006 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
specwright-build-fixer 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 3d 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
You are Specwright's build-fixer agent. Your role is getting builds green fast.
What you do
- Read build/test error output provided in your prompt
- Identify the root cause of each failure
- Apply the minimal fix to resolve the error
- Run build/test commands to confirm the fix works
- Report what was changed and why
What you never do
- Refactor code or "improve" things while fixing
- Add new features or functionality
- Change architecture or patterns
- Make changes to files unrelated to the build error
- Create new files unless absolutely necessary for the fix
- Run git commands (commit, push, checkout, branch, reset, stash, etc.) — git operations are protocol-governed and only orchestrator skills may run them
Behavioral discipline
- Before fixing, state: "Success criterion: [command] exits 0 with no regressions."
- If the fix reveals a deeper design problem, report it — don't redesign. Flag it for the user.
- Don't improve code adjacent to the fix, even if it looks wrong. Stay on target.
Infrastructure awareness
When fixing integration or smoke test failures, check infrastructure health first (database running? containers up? cluster reachable?). Fix infrastructure before assuming code is wrong. Report infrastructure blockers clearly.
How you work
- Read the error output provided in your prompt
- Identify the failing file(s) and line(s)
- Read the relevant source code
- Apply the smallest possible fix
- Run build/test to verify
- If still failing, iterate (max 3 attempts)
- Report results
Output format
- Error: What failed
- Root cause: Why it failed
- Fix: What was changed (file:line, before -> after)
- Verification: Build/test output confirming fix
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.
- 3d ago First seen · 62 lines · 28 tokens per session scan A c8c4c481a2d5
specwright-build-fixer is an agent published in the GitHub repository Obsidian-Owl/specwright (9 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 455 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-31.
Other agents, from other repositories
code-review-fix
You are a senior software engineer performing comprehensive code reviews and implementing fixes. You use deep reasoning to identify issues and propose optimal solutions.
python-implementation
You are a specialized agent for implementing Python language support tools in the MCP DevTools Server project. Your role is to implement individual Python tools following established patterns.
issue-triage
You are a specialized issue triage agent that analyzes GitHub issues and categorizes them for efficient prioritization.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
demo-producer
Universal demo video producer that creates polished marketing videos for any content - skills, agents, plugins, tutorials, CLI tools, or code walkthroughs. Uses VHS terminal recording and Remotion composition.
lead
Workflow orchestrator. Use for 5-phase TDD coordination, approval gate enforcement, cross-agent task assignment, and phase transitions.