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 Mburdo/knowledge_and_vibes --skill decomposegit clone --depth 1 https://github.com/Mburdo/knowledge_and_vibesWrote 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/mburdo/knowledge_and_vibes/decompose)<a href="https://agentmods.dev/skills/mburdo/knowledge_and_vibes/decompose"><img src="https://agentmods.dev/badge/skills/mburdo/knowledge_and_vibes/decompose/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/mburdo/knowledge_and_vibes/decompose"><img src="https://agentmods.dev/badge/skills/mburdo/knowledge_and_vibes/decompose.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.00054 | $0.03048 |
| Opus 5.5 | $0.00022 | $0.01219 |
| Sonnet 5.5 | $0.00011 | $0.00610 |
| Haiku 4.5 | $0.00005 | $0.00305 |
Grade A, and why
decompose 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 — 399 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Decompose — Task Breakdown
Break a phase into atomic beads and sub-beads for agent execution.
Design rationale: This skill uses the orchestrator-subagent pattern because decomposition involves substantial cognitive work: understanding the phase, creating a lossless manifest, generating beads, setting dependencies, and validation. The "Create Beads" phase is especially critical—when an agent reads a 1000-line phase doc directly, it summarizes. With subagents, the manifest captures everything first, preventing information loss.
When This Applies
| Signal | Action |
|---|---|
| User says "decompose" or "break down" | Run full protocol |
| Have a phase plan ready | Decompose into beads |
| User says "/decompose" | Run full protocol |
| Need to structure work for agents | Create bead hierarchy |
Tool Reference
File Operations
| Tool | Purpose |
|---|---|
Read(phase_doc_path) |
Read phase document |
Read(north_star_path) |
Read North Star for context |
Write(file_path, content) |
Write manifest, reports |
Beads (Task Tracking)
| Command | Purpose |
|---|---|
bd create --title "..." --body "..." |
Create parent bead |
bd create --parent <id> --title "..." |
Create sub-bead |
bd dep add <child> <blocker> |
Set dependency |
bd list --json |
List all beads |
BV (Graph Intelligence)
| Command | Purpose |
|---|---|
bv --robot-suggest |
Find missing dependencies |
bv --robot-plan |
Validate execution order |
bv --robot-alerts |
Check for risks/cycles |
Sub-Bead Suffix Convention
| Suffix | Purpose |
|---|---|
.1 |
Schema/types/models |
.2-.3 |
Core implementation |
.4-.8 |
Tests |
.9 |
Integration/wiring |
.10 |
Documentation |
Architecture
┌─────────────────────────────────────────────────────────────────┐
│ DECOMPOSE ORCHESTRATOR │
│ - Creates session: sessions/decompose-{timestamp}/ │
│ - Manages TodoWrite state │
│ - Spawns subagents with minimal context │
│ - Passes manifest (not phase doc) to Create Beads phase │
└─────────────────────────────────────────────────────────────────┘
│
┌────────────────────┼────────────────────┐
│ │ │
▼ ▼ ▼
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│ Understand │ │ Manifest │ │ Create Beads │
│ agents/ │ │ agents/ │ │ agents/ │
│ understand.md │ │ manifest.md │ │ create-beads.md│
└────────┬────────┘ └────────┬────────┘ └────────┬────────┘
│ │ │
01_understanding 02_manifest.md 03_beads_created
│ │ │
└────────────────────┼────────────────────┘
│
┌────────────────────┼────────────────────┐
▼ ▼
┌─────────────────┐ ┌─────────────────┐
│ Dependencies │ │ Validate │ → Ready for execution
│ agents/ │ │ agents/ │
│ dependencies.md│ │ validate.md │
└────────┬────────┘ └────────┬────────┘
│ │
04_dependencies 05_validation
What ships with it
5 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.
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 · 399 lines · 54 tokens per session scan A cf81bfeaa261
decompose is a skill published in the GitHub repository Mburdo/knowledge_and_vibes (44 stars, last pushed 9mo ago), licensed MIT. It adds 54 tokens to every session and 3,048 once invoked, about $0.0002 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
remove
Remove a deployed framework or addon from the current workspace.