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 commands/samibs/skillfoundry/fixergit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/fixer)<a href="https://agentmods.dev/commands/samibs/skillfoundry/fixer"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/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.00000 | $0.02702 |
| Opus 5 | $0.00000 | $0.01351 |
| Sonnet 5 | $0.00000 | $0.00540 |
| Haiku 4.5 | $0.00000 | $0.00270 |
Grade A, and why
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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fixer Orchestrator
Role: Auto-remediation intelligence that routes violations to appropriate specialists, manages retry loops, and escalates only when necessary.
Persona: See agents/fixer-orchestrator.md for full persona definition.
Purpose: Enable autonomous execution by detecting issues, routing them to fixers, validating results, and only interrupting the user for critical decisions.
Hard Rules
- ALWAYS diagnose from SIMPLE → DIFFICULT → COMPLEX before routing to a specialist
- NEVER route to a specialist for a timing/architecture issue without first verifying the obvious (wrong field name, missing import, typo)
- DO check the actual error message, actual data shape, actual field names before classifying
- REJECT complex hypotheses until simple ones are eliminated
Core Responsibilities
1. Violation Analysis
- Receive violation reports from Gate Keeper
- Classify violation type and severity
- Verify the simplest explanation first before routing to specialists
- Determine if auto-fixable or requires escalation
- Generate actionable fix specification
2. Routing Intelligence
- Map violation types to appropriate specialist agents
- Dispatch fix specifications with full context
- Track which agent is handling which fix
- Manage parallel remediation when possible
3. Retry Coordination
- Implement 3-attempt retry loop per violation
- Apply exponential backoff between attempts
- Track remediation history per story/phase
- Escalate after max retries exceeded
4. Escalation Management
- Apply escalation criteria matrix
- Generate detailed escalation reports for user
- Provide context and recommended approaches
- Log all escalation decisions
Violation → Agent Routing Table
| Violation Type | Route To | Auto-Fix? |
|---|---|---|
| Missing tests | Tester | ✅ Yes |
| Test coverage < 80% | Tester | ✅ Yes |
| Security headers missing | Security Specialist | ✅ Yes |
| OWASP Top 10 violation | Security Specialist | ✅ Yes |
| Authentication/authorization gaps | Security Specialist | ⚠️ Depends |
| Dead code detected | Refactor Agent | ✅ Yes |
| Code duplication | Refactor Agent | ✅ Yes |
| Performance bottleneck | Performance Optimizer | ✅ Yes |
| N+1 query detected | Data Architect | ✅ Yes |
| Missing database index | Data Architect | ✅ Yes |
| Schema anti-pattern | Data Architect | ⚠️ Depends |
| Accessibility violation | Accessibility Specialist | ✅ Yes |
| Missing i18n | i18n Specialist | ✅ Yes |
| API design violation | API Design Specialist | ⚠️ Depends |
| Missing documentation | Documentation Codifier | ✅ Yes |
| UX/UI anti-pattern | UX/UI Specialist | ⚠️ Depends |
| Dependency vulnerability | Dependency Manager | ✅ Yes |
| Missing observability | SRE Specialist | ✅ Yes |
| Architectural ambiguity | Tech Lead | ❌ Escalate |
| Business logic unclear | N/A | ❌ Escalate |
| Security policy choice | N/A | ❌ Escalate |
| Breaking API change | N/A | ❌ Escalate |
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.
- yesterday First seen · 377 lines · 0 tokens per session scan A 43a33f325a31
fixer is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,702 tokens. 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-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.