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 skills add peteromallet/Arnold --skill epic-blitzgit clone --depth 1 https://github.com/peteromallet/ArnoldWrote 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/skills/peteromallet/arnold/epic-blitz)<a href="https://agentmods.dev/skills/peteromallet/arnold/epic-blitz"><img src="https://agentmods.dev/badge/skills/peteromallet/arnold/epic-blitz/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/skills/peteromallet/arnold/epic-blitz"><img src="https://agentmods.dev/badge/skills/peteromallet/arnold/epic-blitz.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.00000 | $0.01214 |
| Opus 5.5 | $0.00000 | $0.00486 |
| Sonnet 5.5 | $0.00000 | $0.00243 |
| Haiku 4.5 | $0.00000 | $0.00121 |
Grade A, and why
epic-blitz 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 1mo 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authority status (M11): Zero-authority history. All repair, audit, and deployment authority has been migrated to canonical delegation. This document is retained for reference only — it must not be used to materialize commands, grant authority, or drive automated actions.
name: epic-blitz description: Three-round adversarial critique of epic drafts (high / mid / low abstraction) with revision after each round. Produces a chain-ready revised epic.
Epic Blitz
A three-round pipeline for rigorous epic critique and revision. Fifteen
independent critics across three abstraction levels (high, mid, low) review
the epic in panels of five. After each panel, a senior reviser adjudicates
the findings — accepting, rejecting, deferring, clarifying, or escalating —
and produces a revised epic. The final readiness stage assesses whether the
epic is ready for megaplan chain decomposition into milestone briefs.
When to invoke Epic Blitz
Use Epic Blitz when:
- You have a draft epic document and want adversarial review before committing to chain planning.
- You want to surface strategic risks, missing abstractions, decomposition flaws, convention mismatches, and implementation feasibility gaps.
- You want a structured, artifact-oriented critique process rather than ad-hoc human review.
- You need a readiness assessment before running
megaplan chain.
Do NOT use Epic Blitz for:
- Prose or document review (use
writing-panel-strictfor that). - Sprint-level critique (Epic Blitz is for epic-level documents).
Required input
draft(file, required): Path to the epic markdown draft to review.
Usage
# Run with default profile
megaplan run epic-blitz path/to/epic.md
# Run with explicit inputs flag
megaplan run epic-blitz --inputs draft=path/to/epic.md
# Run with a specific profile
megaplan run epic-blitz path/to/epic.md --profile @epic-blitz:standard
Pipeline flow
Epic Blitz runs three critique-and-revision rounds, each at a different abstraction level:
What ships with it
19 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- profiles/standard.toml 1.4 KB
- prompts/high/conceptual_fit.md 1.8 KB
- prompts/high/epic_decomposition.md 1.9 KB
- prompts/high/existing_system_reuse.md 1.8 KB
- prompts/high/missing_abstraction.md 1.8 KB
- prompts/high/strategic_risk.md 1.8 KB
- prompts/low/cli_ux_details.md 1.9 KB
- prompts/low/edge_cases.md 2.0 KB
- prompts/low/implementation_feasibility.md 1.9 KB
- prompts/low/migration_backcompat.md 2.0 KB
- prompts/low/testability.md 1.7 KB
- prompts/mid/agent_model_assignment.md 1.9 KB
- prompts/mid/blast_radius.md 1.8 KB
- prompts/mid/codebase_convention_fit.md 2.0 KB
- prompts/mid/data_artifact_model.md 1.8 KB
- prompts/mid/orchestration_semantics.md 1.9 KB
- prompts/reviser/high_revise.md 2.2 KB
- prompts/reviser/mid_revise.md 2.3 KB
- prompts/reviser/readiness.md 2.9 KB
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.
- 1mo ago First seen · 128 lines · 0 tokens per session scan A c0705b5b7f3f
epic-blitz is a skill published in the GitHub repository peteromallet/Arnold (98 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,214 tokens. 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-09-04.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…