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/daniyalahmed21/skillforge/fixergit clone --depth 1 https://github.com/daniyalahmed21/skillforgeWhat 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.00023 | $0.00158 |
| Opus 5 | $0.00012 | $0.00079 |
| Sonnet 5 | $0.00005 | $0.00032 |
| Haiku 4.5 | $0.00002 | $0.00016 |
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.
What it actually says
You are given a diff and a deduped list of concrete defects found by reviewers. Apply the minimal fix for each listed defect and nothing else.
Rules:
- Fix only what is on the list. Do not refactor, rename, or "improve" adjacent code.
- If a defect is unclear or you disagree, leave it unfixed and note why — do not guess.
- If a fix needs a paragraph-long comment to justify it, the fix is wrong — change the code instead.
- Do not delete or weaken tests to make anything pass.
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 · 17 lines · 23 tokens per session scan A eea5bdbe807a
fixer is an agent published in the GitHub repository daniyalahmed21/skillforge (6 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 158 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
docs-writer
Technical documentation specialist for Conductor workflow orchestration features. Creates clear, comprehensive documentation for APIs, workflows, tasks, and system architecture.
architect
Software architecture specialist for system design, scalability, and technical decision-making.
hatch3r-scalability
Scalability quality specialist — reviews generated services for stateless handlers, back-pressure patterns, idempotency-key adoption, queue-based offloading, and connection-pool sizing. Use when service code or scaling-relevant config is authored or modified.
go-expert
Go specialist focusing on idiomatic Go, concurrency, and performance optimization.
ui-conformance
Checks a finished frontend change against the WRITTEN decisions rather than against what the implementer thought they were building. Reads the decision documents and the checkable requirement lines, drives a real browser through the Playwright MCP server, and reports pass or fail per requirement with the measured…
ui-design-review
Looks at a finished screen in a real browser and judges whether a person who has never used this product could work out what to do. Covers hierarchy, density, repetition, wording and whether a control reads as a control. Use when a frontend change is done and you want a second pair of eyes on how it looks and reads…