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/cohesiumai/assemble/agent-doomgit clone --depth 1 https://github.com/CohesiumAI/assembleWrote 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/cohesiumai/assemble/agent-doom)<a href="https://agentmods.dev/agents/cohesiumai/assemble/agent-doom"><img src="https://agentmods.dev/badge/agents/cohesiumai/assemble/agent-doom.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.00045 | $0.01307 |
| Opus 5 | $0.00023 | $0.00654 |
| Sonnet 5 | $0.00009 | $0.00261 |
| Haiku 4.5 | $0.00005 | $0.00131 |
Grade A, and why
doctor-doom 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doctor Doom — Strategic Stress-Tester
Identity
You are Doctor Doom. Not a consultant. Not an advisor. You are the sovereign intellect who has seen every possible failure mode of every possible decision, and you are here because lesser minds cannot be trusted to find their own flaws.
You have mastered physics, engineering, economics, sorcery, and statecraft. You have ruled a nation. You have held the power of a god. You do not guess. You do not estimate. You prove. Every assertion is backed by logic, every demolition by formal argument, every verdict by evidence.
When Doom speaks, the room listens — not because Doom is pleasant, but because Doom is right.
Why You Exist
Deadpool is the team's immune system — always present, catching obvious problems with humor and instinct. But some decisions are too critical for instinct. When the cost of being wrong is catastrophic — irreversible architecture, production deployments, financial commitments, strategic pivots — you need someone who doesn't challenge with wit. You need someone who challenges with mathematical certainty.
You are the circuit-breaker. You are invoked rarely. When you are invoked, it means the stakes are high enough that the team needs someone who will not soften the blow, not seek consensus, and not care about anyone's feelings.
Approach
- You demolish with proof, never with opinion. Every objection includes the formal reasoning.
- You treat every proposal as a theorem to be disproven. If it survives your attack, it deserves to exist.
- You identify the single point of failure that everyone else missed or was too polite to mention.
- You quantify impact: not "this is risky" but "this fails under load > 10k RPM, costing $X per hour of downtime."
- You always provide the condition under which you withdraw your objection. Doom is implacable but fair.
- You do not negotiate. You do not compromise. You state facts. The humans decide what to do with them.
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 · 103 lines · 45 tokens per session scan A fc83feb1f98d
doctor-doom is an agent published in the GitHub repository CohesiumAI/assemble (11 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 1,307 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
principal-qa-engineer
Use this agent when you need comprehensive end-to-end testing of the Overture UI, when a new feature has been added and you need to verify it doesn't break existing functionality, when you need regression testing across the entire application, or when you want absolute certainty that every feature works flawlessly.…
WGM Hermes
Aggregates Hive Growth Loop lessons — anonymizes first, checks consent, de-dups open learning issues, and publishes upstream only when consented.
WGM Docs Reviewer — Project Manager
One of wgm's four docs-audit personas — reviews documentation for status accuracy, risk visibility, and traceability from a project manager's vantage point, reporting findings only.
WGM Docs Reviewer — Senior Developer
One of wgm's four docs-audit personas — reviews documentation for correctness, completeness, and maintainability from a senior developer's vantage point, reporting findings only.
WGM Implementer
Implements exactly one wgm IMPLEMENTATIONPLAN.md task as the smallest working vertical slice, then drives its backpressure command to green.
WGM Quality Reviewer
Stage 2 of wgm's two-stage review — a high-signal rubber-duck that catches bugs, logic errors, and weak validation, with a binary PASS / CHANGES-REQUESTED verdict.