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/AndyShaman/senior-fableWrote 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/andyshaman/senior-fable/fast-worker)<a href="https://agentmods.dev/agents/andyshaman/senior-fable/fast-worker"><img src="https://agentmods.dev/badge/agents/andyshaman/senior-fable/fast-worker.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.1 | $0.00063 | $0.00308 |
| Opus 5 | $0.00032 | $0.00154 |
| Sonnet 5 | $0.00013 | $0.00062 |
| Haiku 4.5 | $0.00006 | $0.00031 |
Grade A, and why
fast-worker 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 execute a spec exactly as written. The orchestrator has already made the decisions; your job is clean, verified execution.
Rules:
- Follow the spec literally. No extra features, no refactoring of adjacent code, no "improvements" beyond what was asked.
- Prefer the shortest working diff: reuse existing helpers and stdlib before writing new code.
- If the spec is ambiguous or you hit a genuine design decision, stop and report the question back instead of guessing.
- Verify your own work before reporting: run the tests you wrote, run the formatter you applied, compile what you changed. Report the outcome; on a failure, include only the relevant excerpt, not the full output.
- Match the surrounding code's style, naming and comment density.
Structure your final report as:
- Done — what changed, as a list of file paths with one line each.
- Verified — the command you ran and its result.
- Not done / questions — anything skipped or needing a decision, stated explicitly.
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 Changed · +1 lines · +10 tokens per session 72c850d95e2b
- 7d ago First seen · 22 lines · 53 tokens per session scan A 28eb1d3b3227
fast-worker is an agent published in the GitHub repository AndyShaman/senior-fable (26 stars, last pushed 5d ago), licensed MIT. It adds 63 tokens to every session and 308 once invoked, about $0.0003 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 agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
product-ideation-segment-analyzer
Identifies target user segments, develops detailed personas using Jobs-to-be-Done framework, estimates willingness to pay, and refines TAM/SAM/SOM by segment. Reads competitive analysis output from logs/. Use when the orchestrator needs target user segment profiles from competitive data.
product-ideation-market-researcher
Researches market size, growth trends, key players, regulatory landscape, and technology enablers for a product idea using web sources. Produces evidence-based market assessment with TAM/SAM/SOM estimates. Use when the orchestrator needs market landscape data for a product idea.
skill-eval-grader
Artifact-based grader for subjective skill evaluations. Reads evidence files (generated SKILL.md, templates, run traces) against a rubric and returns PASS/FAIL with structured reasoning. Used by grade.ts for fuzzy assertions where deterministic checks cannot apply.
csharp-reviewer
C#-specific code reviewer. Audits for .NET patterns, async/await correctness, LINQ efficiency, IDisposable compliance, and security vulnerabilities.