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 skills/flyfission/nuclear-grade-context-engineering/breaking-down-the-worknpx skills add FlyFission/nuclear-grade-context-engineering --skill breaking-down-the-workgit clone --depth 1 https://github.com/FlyFission/nuclear-grade-context-engineeringWrote 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/flyfission/nuclear-grade-context-engineering/breaking-down-the-work)<a href="https://agentmods.dev/skills/flyfission/nuclear-grade-context-engineering/breaking-down-the-work"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/breaking-down-the-work.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.00084 | $0.02516 |
| Opus 5 | $0.00042 | $0.01258 |
| Sonnet 5 | $0.00017 | $0.00503 |
| Haiku 4.5 | $0.00008 | $0.00252 |
Grade A, and why
breaking-down-the-work 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 5d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Breaking Down the Work
Overview
A work breakdown (WBS) splits one deliverable into smaller pieces someone can own, with no gaps and no overlaps, plus a dictionary that defines every piece. "Product-first" means the pieces are the things you build (nouns), not the actions you take (verbs). The work breakdown is the spine that estimates, folders, ownership, and traceability hang from.
Three things can wreck it. Under-coverage: some scope is orphaned and no one owns it. Over-coverage: invented or gold-plated scope that no one asked for. And a third drift where verbs pose as the backbone and hide products that are actually missing. This skill holds two rules: the 100% rule (the pieces add up to exactly the whole, no more and no less) and no overlaps. It also forces a dictionary entry for every piece. That way the breakdown can be reviewed before any folder or line of code exists.
Decision contract
- Claim checked: product-first children cover exactly the parent (100% rule), no two siblings overlap, every outline number has a filled dictionary entry.
- Artifact observed: the one-line deliverable, mission anchor, and
templates/standard/wbs.md-> an outline-numbered table, per-piece dictionary, and handoff to folders and each leaf'splan.md. - Decision affected: block -- plan-ready vs not: do the children sum to 100% with no gaps and no overlaps (MECE).
- Failure class: non-mece-breakdown (orphaned scope, invented scope, or overlap with no stated gap).
- Next action: name the gap or re-cut the boundary; escalate to the owner when children cannot add up without overlap.
When to Use
- An epic, feature, or new subsystem needs breaking down before planning or layout.
- A folder tree or repo structure is about to be designed and needs a scope basis you can defend.
- Scope keeps growing and no one can say whether the plan is complete or has overlaps.
- Several agents or people need one shared map of the work with no overlaps.
- A
.nuclear/changes/<slug>/packet needs its inside structure decided on principle.
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.
- 5d ago First seen · 140 lines · 84 tokens per session scan A e082879c14c8
breaking-down-the-work is a skill published in the GitHub repository FlyFission/nuclear-grade-context-engineering (33 stars, last pushed 26d ago), licensed MIT. It adds 84 tokens to every session and 2,516 once invoked, about $0.0004 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 skills, from other repositories
contextlock
Safely inspect a repository through the ContextLock MCP server. Use when exploring, searching, reviewing, or auditing repository files with ContextLock, especially before reading unfamiliar code or when sensitive files and secrets may be present.
kami-deck
A lab-meeting deck on gut-microbiome links to sleep quality — the design, the results, the caveats, and the next experiment. Built as a decision-grade academic research deck for lab group, PI.
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
fs-editorial-forest
Art-directing a fashion house's annual report — the editorial system, the photography rhythm, and the data spreads. Built as a decision-grade design craft deck for brand stakeholders, exec audience.
simple-deck
OpenDesign's operating review: growth, burn, and the concrete path to sustainability without losing the open ethos. Built as a decision-grade corporate strategy deck for leadership team.
html-ppt-zhangzara-coral
OpenDesign's community-growth campaign across GitHub, Discord, and X: the loops, the content calendar, and the pipeline math. Built as a decision-grade marketing & GTM deck for growth team, community lead.