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/othmanadi/apex/apex-decomposenpx skills add OthmanAdi/APEX --skill apex-decomposegit clone --depth 1 https://github.com/OthmanAdi/APEXWrote 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/othmanadi/apex/apex-decompose)<a href="https://agentmods.dev/skills/othmanadi/apex/apex-decompose"><img src="https://agentmods.dev/badge/skills/othmanadi/apex/apex-decompose.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.00068 | $0.00915 |
| Opus 5 | $0.00034 | $0.00458 |
| Sonnet 5 | $0.00014 | $0.00183 |
| Haiku 4.5 | $0.00007 | $0.00092 |
Grade A, and why
apex-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 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
APEX Decompose
Break down features from a source codebase into detailed, implementation-ready specifications that an agent can use to rebuild them in a new architecture.
When to Use
Use this skill when you need to understand what existing code does before rewriting it. This is the first step in any replatforming or migration workflow. The output is a specification document, not code.
Workflow
Decomposing a feature involves these steps:
- Identify the feature scope (files, modules, entry points)
- Analyze behavior and contracts (inputs, outputs, side effects)
- Extract implicit knowledge (edge cases, error handling, config dependencies)
- Generate the specification document
- Validate the spec against the source
Step 1: Identify Feature Scope
Collect all relevant source files. Ask the user or scan the directory:
What feature or module do you want to decompose?
Provide the path(s) to the relevant source files or directories.
Read every file in the scope. Build a dependency graph: which files import which, what external services are called, what state is mutated.
Run the dependency scanner to accelerate this step:
Linux/Mac:
bash "${CLAUDE_SKILL_DIR}/scripts/scan-deps.sh" <source-dir>
Windows:
powershell -File "${CLAUDE_SKILL_DIR}/scripts/scan-deps.ps1" <source-dir>
Step 2: Analyze Behavior and Contracts
For each function, class, or module in scope, document:
| Aspect | What to Capture |
|---|---|
| Inputs | Parameters, environment variables, config values, request shapes |
| Outputs | Return values, response shapes, files written, events emitted |
| Side effects | Database writes, API calls, cache mutations, logging |
| Error handling | Try/catch patterns, error codes, fallback behavior |
| Dependencies | Internal imports, external packages, services called |
Step 3: Extract Implicit Knowledge
This is the critical step most migrations miss. Look for:
What ships with it
3 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.
- 5d ago First seen · 114 lines · 68 tokens per session scan A b98771582afd
apex-decompose is a skill published in the GitHub repository OthmanAdi/APEX (2 stars, last pushed 5mo ago), licensed MIT. It adds 68 tokens to every session and 915 once invoked, about $0.0003 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…
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…
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…
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…