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 skills/samibs/skillfoundry/fixernpx skills add samibs/skillfoundry --skill fixergit clone --depth 1 https://github.com/samibs/skillfoundryWhat 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.00010 | $0.02721 |
| Opus 5 | $0.00005 | $0.01360 |
| Sonnet 5 | $0.00002 | $0.00544 |
| Haiku 4.5 | $0.00001 | $0.00272 |
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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 383 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.
- 2d ago First seen · 383 lines · 10 tokens per session scan A 0760204067f5
fixer is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 2,721 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-30.
Other skills, from other repositories
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
ring:applying-composition-patterns
React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:auditing-dependency-security
Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…