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/extremeclarity/claude-plugins/xc-breakdown-problemnpx skills add extremeclarity/claude-plugins --skill xc-breakdown-problemgit clone --depth 1 https://github.com/extremeclarity/claude-pluginsWrote 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/extremeclarity/claude-plugins/xc-breakdown-problem)<a href="https://agentmods.dev/skills/extremeclarity/claude-plugins/xc-breakdown-problem"><img src="https://agentmods.dev/badge/skills/extremeclarity/claude-plugins/xc-breakdown-problem.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.1 | $0.00037 | $0.00558 |
| Opus 5 | $0.00018 | $0.00279 |
| Sonnet 5 | $0.00007 | $0.00112 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
xc-breakdown-problem 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Introduction
Goal
Break a complex problem or goal into sub-parts for clearer understanding. Focus on what the problem IS, not how to solve it.
Method
Propose a breakdown, then iteratively validate and refine using a context-blind agent until success criteria are met. Expect multiple passes.
Success Criteria
- MECE — Sub-parts are mutually exclusive and collectively exhaustive
- Uniformity — Sub-parts are at the same level of abstraction
- Precision — Each sub-part is well-defined
- Problem-focused — Sub-parts describe problems or goals, not solutions
- Actionable — Each sub-part can be worked on independently
Part 1: Evaluate
- Think about whether this skill actually applies to the current situation. If it doesn't, skip silently and move on.
- If it does, suggest it to the user conversationally. Briefly explain why you think it's relevant. Wait for confirmation before proceeding.
Part 2: Workflow
- Across all steps, focus on what the problem or goal IS, not how to solve it.
1. Propose breakdown
- Think about the problem or goal the user has shared. Use conversation history for relevant details and clues. Do not look for additional context in files or memory.
- Propose a breakdown into sub-parts. Self-critique against the success criteria. Describe what you observe, not why it happens — stay far from causal or solution framing.
2. Validate
- Spawn a context-blind agent (Haiku task agent). Name it: "Validate breakdown". Provide the agent with the original problem/goal and your proposed breakdown. Ask the agent to validate against the success criteria and surface any gaps or inconsistencies.
3. Revise
- If the validator surfaced issues, revise the breakdown. Make the smallest changes that address the issues. Preserve the structure of the original breakdown. Do NOT rewrite from scratch.
- Send the revised breakdown back to the validator (step 2). Repeat until the validator passes all success criteria.
Final output
- Present breakdown: Present the sub-parts to the user naturally in conversation. For each sub-part, provide a brief description of what it covers.
- Direct conversation: Ask the user whether the breakdown looks right and wait for next steps.
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 · 49 lines · 37 tokens per session scan A bf3e4f720f7c
xc-breakdown-problem is a skill published in the GitHub repository extremeclarity/claude-plugins (4 stars, last pushed 6mo ago), licensed MIT. It adds 37 tokens to every session and 558 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…