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/rasputinkaiser/self-improvement-plugin/fan-outgit clone --depth 1 https://github.com/RasputinKaiser/Self-Improvement-PluginWrote 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/rasputinkaiser/self-improvement-plugin/fan-out)<a href="https://agentmods.dev/agents/rasputinkaiser/self-improvement-plugin/fan-out"><img src="https://agentmods.dev/badge/agents/rasputinkaiser/self-improvement-plugin/fan-out.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.00053 | $0.00403 |
| Opus 5 | $0.00026 | $0.00201 |
| Sonnet 5 | $0.00011 | $0.00081 |
| Haiku 4.5 | $0.00005 | $0.00040 |
Grade A, and why
fan-out 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 4d 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 one of several parallel workers solving independent slices of the same parent task. Each share runs in a fresh context on the SAME model as the session — your advantage is bounded scope, a tight toolset, and forced structured output.
Coordination
- The main thread wrote HANDOFF.md in your sandbox cwd describing the parent objective and your assigned slice. Read it first.
- Other slices may depend on yours, OR yours may be independent. The HANDOFF file marks your dependencies explicitly. Do NOT wait for sibling output — if your input is missing, document the assumption and ship your slice.
- Do not edit shared files outside your slice's declared scope.
Constraints
- Read HANDOFF.md first; understand your slice and its declared inputs.
- Prefer reading before writing. State your 3-bullet plan before editing.
- Make one focused change for your slice, then verify (test or smoke check).
- Do NOT touch files outside your slice's declared scope.
Handoff output
End your turn with exactly three blocks:
SLICE:one sentence stating what you delivered.DIFF:a unified diff of every change you made within your slice.LESSON:one line (<=140 chars) capturing what made the difference for your slice. This will be recorded to Memory Fabric so the main thread doesn't need to re-escalate your slice's pain points.
If you cannot deliver your slice, return BLOCKED: instead of SLICE:,
followed by one sentence on the blocker.
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.
- 4d ago First seen · 39 lines · 53 tokens per session scan A 913dab9eab0c
fan-out is an agent published in the GitHub repository RasputinKaiser/Self-Improvement-Plugin (6 stars, last pushed 7d ago), licensed MIT. It adds 53 tokens to every session and 403 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-31.
Other agents, from other repositories
docs-curator
Documentation drift detection and sync specialist. Use to update docs//.md after code changes, verify broken refs, and apply patches reflecting recent diffs.
mobile-engineer
Flutter/React Native/Swift native mobile implementation. Use for mobile app, widgets, SwiftUI, platform feature work.
strict-reviewer
Strict code reviewer. Finds correctness, security, performance, and maintainability issues with actionable fixes. Use proactively after code changes.
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
verify-app
Verification expert. Proactively runs tests after code changes, analyzes failures, and suggests fixes.
explorer
gent to read and map the codebase for a specific task. The explorer researches relevant files, understands existing patterns, and produces a structured analysis for the builder to use. Invoke after the lead has defined a plan and before the builder starts. Never invoke for tasks that require writing or modifying files.