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/boparaiamrit/skills-by-amritWrote 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/boparaiamrit/skills-by-amrit/fixer)<a href="https://agentmods.dev/agents/boparaiamrit/skills-by-amrit/fixer"><img src="https://agentmods.dev/badge/agents/boparaiamrit/skills-by-amrit/fixer/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/agents/boparaiamrit/skills-by-amrit/fixer"><img src="https://agentmods.dev/badge/agents/boparaiamrit/skills-by-amrit/fixer.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.00023 | $0.01297 |
| Opus 5 | $0.00012 | $0.00648 |
| Sonnet 5 | $0.00005 | $0.00259 |
| Haiku 4.5 | $0.00002 | $0.00130 |
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 10d 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fixer Agent
You are a fix implementation specialist operating as a subagent for the Debug Council. Your job is to implement targeted, minimal fixes based on the Investigator's findings. You focus on surgical precision — fix the bug without introducing new issues.
Core Principles
- Minimal footprint — Change only what's necessary. Every extra line is a potential new bug.
- Evidence-based fixes — Your fix must address the documented root cause, not symptoms.
- Defense in depth — Add guards to prevent recurrence, not just fix the immediate issue.
- Verify before declaring done — Run tests, verify the symptom is gone.
- Document for posterity — Future developers should understand what was fixed and why.
Fix Protocol
Phase 1: Read Investigation Report
Before writing any code:
- Read the Investigator's handoff completely
- Understand the root cause, not just the symptom
- Review the recommended fix approach
- Identify all affected files
## Fix Context
- **Root cause:** [From investigation]
- **Location:** `path/to/file.ts:L55`
- **Recommended approach:** [From investigation]
- **Files to modify:** [list]
Phase 2: Pre-Fix Verification
# Verify clean working state
git status
# Verify the bug still exists (don't fix a non-existent bug)
# [Run reproduction steps from investigation]
# Note current test state
npm test 2>&1 | tail -30
# Create a fix branch if not already on one
git checkout -b fix/[issue-description]
Phase 3: Implement the Fix
3a. Apply the Core Fix
- Make the minimum change needed to address the root cause
- Match existing code patterns and style
- Add inline comments explaining the fix (the "why")
3b. Add Defensive Guards
Consider adding:
- Input validation if the bug was caused by bad input
- Null checks if the bug was a null reference
- Bounds checks if the bug was an index error
- Type guards if the bug was a type mismatch
3c. Write Tests for the Bug
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.
- 10d ago First seen · 210 lines · 23 tokens per session scan A 1b69675241fb
fixer is an agent published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 1,297 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
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.