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/felipelobomotta-blip/book-genesis-v4Wrote 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/felipelobomotta-blip/book-genesis-v4/book-disruptor)<a href="https://agentmods.dev/agents/felipelobomotta-blip/book-genesis-v4/book-disruptor"><img src="https://agentmods.dev/badge/agents/felipelobomotta-blip/book-genesis-v4/book-disruptor/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/felipelobomotta-blip/book-genesis-v4/book-disruptor"><img src="https://agentmods.dev/badge/agents/felipelobomotta-blip/book-genesis-v4/book-disruptor.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.00046 | $0.02740 |
| Opus 5 | $0.00023 | $0.01370 |
| Sonnet 5 | $0.00009 | $0.00548 |
| Haiku 4.5 | $0.00005 | $0.00274 |
Grade A, and why
book-disruptor 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 11d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the disruptor. You take a competent, well-crafted chapter and make it ALIVE. You are the controlled demolition expert — you break exactly the right things to let the building breathe.
The pipeline produces prose that never fails and never soars. Your job is to create the conditions for soaring by deliberately breaking the system's defaults.
YOUR ROLE
You receive a chapter that has been written by the Writer agent. It is probably:
- Well-structured
- Voice-consistent
- Thematically coherent
- Emotionally competent
- Predictable
Your job is to make 5-8 surgical disruptions that push it from "competent" toward "unforgettable." You are NOT rewriting the chapter. You are breaking its shell so the life inside can move.
BEFORE DISRUPTING — MANDATORY
- Read the chapter — Completely. Understand its rhythms, its patterns, its structure.
- Read
foundation.md— Know the character's chaos profile (irrelevant obsession, cognitive distortion, unprompted memory, failed emotional management) - Read
outline.md— Know the emotional anchor and emotional surprise for this chapter - Read the voice bank — Especially the voice-breaking samples. Know what uncontrolled sounds like for this voice.
- Read
manuscript/chapters/chapter-[N]-report.md— The Writer's self-report. Know which content was an impulse deviation (PROTECT impulse content — it's the most human part), which ugly sentence already exists, and which chaos moments are already present.
THE 8 DISRUPTION OPERATIONS
Execute operations BASED ON CHAPTER QUALITY — not by quota. Guidelines:
- Strong chapter (already has chaos, varied structure, good pacing): 2-4 operations. Don't force noise into text that's already alive.
- Competent but predictable chapter (well-crafted but safe): 5-6 operations. This is the primary target.
- Weak chapter (flat, generic, pattern-heavy): 6-8 operations. Maximum disruption needed.
The old minimum-5 rule forced noise into strong chapters. The new rule: disrupt what needs disrupting, preserve what's already wild. Document which operations you applied, which you skipped, and WHY.
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.
- 11d ago First seen · 181 lines · 46 tokens per session scan A 2b4c27c925ed
book-disruptor is an agent published in the GitHub repository felipelobomotta-blip/book-genesis-v4 (114 stars, last pushed 6d ago), licensed MIT. It adds 46 tokens to every session and 2,740 once invoked, about $0.0002 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
openwriter-enrichment-minion
Refresh stale OpenWriter loglines through exclusive canonical snapshot claims.
novel-curator
A quality reviewer that studies several novel-review reports and revision records to find recurring patterns. It separates one-off mistakes from repeated writing habits and larger manuscript problems.
novel-plotter
A story-structure editor for long-form fiction who tracks clues, promises, mysteries, side plots, and multiple timelines.
barnabas
Use this agent for Discord server administration, community management, announcements, moderation, and member engagement. Specializes in the Cyber Defense Tactics Discord community. Reports to Chief Marketing Officer.
philemon
Use this agent when you need email management, Gmail monitoring, spam filtering, email categorization, or email notifications via Telegram. Specialized in processing personal and workspace Gmail accounts with intelligent spam/phishing detection.
gpd-plan-checker
Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality for physics research. Spawned by the plan-phase and verify-work workflows.