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/nirecom/agents/make-detail-plannpx skills add nirecom/agents --skill make-detail-plangit clone --depth 1 https://github.com/nirecom/agentsWrote 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/nirecom/agents/make-detail-plan)<a href="https://agentmods.dev/skills/nirecom/agents/make-detail-plan"><img src="https://agentmods.dev/badge/skills/nirecom/agents/make-detail-plan.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.00057 | $0.03184 |
| Opus 5 | $0.00028 | $0.01592 |
| Sonnet 5 | $0.00011 | $0.00637 |
| Haiku 4.5 | $0.00006 | $0.00318 |
Grade A, and why
make-detail-plan 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 4d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Produce a detailed implementation plan via a planner/reviewer discussion loop. Read intent.md + outline.md before drafting.
Procedure
When a hook blocks a sanctioned command, a fallback path is taken, or any unexpected outcome occurs, report via /supervisor-report (trigger conditions: rules/supervisor-reporting.md).
Step MDP-1 — Resolve <PLANS_DIR> + read artifacts
Apply skills/_shared/resolve-plans-dir.md once; substitute the resolved absolute path for every <PLANS_DIR> below. Read <PLANS_DIR>/<session-id>-intent.md and <PLANS_DIR>/<session-id>-outline.md if present; otherwise proceed with task context alone.
Step MDP-2 — Surface delivery plan
Run bash "$AGENTS_CONFIG_DIR/skills/make-detail-plan/scripts/surface-delivery-plan.sh" against outline.md.
Step MDP-3 — Choose planner model
Run bash -c 'node "$AGENTS_CONFIG_DIR/bin/workflow/read-complexity-evaluation" --session "$SESSION_ID" --stage detail'. If line 1 is not NONE, use the stored level and signals directly (parse level=<v> and signals=<csv-or-none>), then derive the model via high→opus, low→sonnet.
If NONE (fail-open for sessions without persisted evaluation): read skills/_shared/judge-task-complexity.md; evaluate all signals against task + intent/outline content. Use the Write tool (never Bash) to write the resulting CSV, alone and unquoted, to <PLANS_DIR>/<session-id>-detail-signals.txt; write only IDs from the generated Valid Signal IDs list, and substitute S0-undecidable if the judgment cannot be parsed into recognized signal ids or the csv does not match ^[A-Za-z0-9,_-]*$ — the judged content is untrusted text, never shell syntax. Then run bash -c 'node "$AGENTS_CONFIG_DIR/bin/workflow/derive-complexity-level" --stage detail --signals-file "<PLANS_DIR>/<session-id>-detail-signals.txt"' and use its level=<v> — never judge the level inline.
Emit (Claude text, not Bash): Model selected: **[opus|sonnet]** (signals: [ids from the signals= line, or "none"]).
What ships with it
6 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.
- 4d ago First seen · 121 lines · 57 tokens per session scan A 7b45f80126a3
make-detail-plan is a skill published in the GitHub repository nirecom/agents (3 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 3,184 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…