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/nicknisi/ideation/execute-specnpx skills add nicknisi/ideation --skill execute-specgit clone --depth 1 https://github.com/nicknisi/ideationWrote 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/nicknisi/ideation/execute-spec)<a href="https://agentmods.dev/skills/nicknisi/ideation/execute-spec"><img src="https://agentmods.dev/badge/skills/nicknisi/ideation/execute-spec.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.00071 | $0.04729 |
| Opus 5 | $0.00036 | $0.02364 |
| Sonnet 5 | $0.00014 | $0.00946 |
| Haiku 4.5 | $0.00007 | $0.00473 |
Grade A, and why
execute-spec 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 3d 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute Ideation Specification
Arguments: $ARGUMENTS
Execute a spec file generated by the ideation skill.
Flags:
--parallel— dispatch subagents for independent components.--headless— auto-proceed through every confirmation (noAskUserQuestion). Used by/ideation:autopilot.--strict— modifies--headlessto fail closed where plain headless fails open. Set by autopilot for express-approved contracts (approvalMode: "express"incontract-data.json), whose artifacts no human reviewed — the fail-open defaults are calibrated for reviewed artifacts.- Remaining argument: spec file path (optional).
Example: /ideation:execute-spec --parallel or /ideation:execute-spec --headless docs/ideation/foo/spec-phase-1.md
Headless/strict gate semantics — owned by workflows/README.md's gate-behavior table; when prose and engine disagree, the tests are right. Do not restate the matrix here — the original defect (strict specified to fail closed, actually improvising) shipped exactly because divergent prose copies drifted from the engine.
Pre-Execution
1. Load Specification
Resolve the spec in this order:
- Argument given — read it directly.
- No argument — auto-detect from
TaskList: a task withstatus: pending, emptyblockedBy, and a subject starting with "Phase" or metadata containingspecFile. Read itsspecFile(viaTaskGet). - No tasks — glob
./docs/ideation/*/spec-phase-*.mdand./docs/ideation/*/spec.md(single-spec projects emit a barespec.md). Multiple matches →AskUserQuestionto pick (headless: first unblocked).
2. Scout Codebase
Under the autopilot Workflow engine, this step is superseded: the engine runs the scout as a sibling workflow stage and hands its map to the build stage under an explicit ENGINE OVERRIDES block (skip scout, stop after Verify, never commit, git add -N every new file) — see ${CLAUDE_PLUGIN_ROOT}/workflows/README.md. This section governs direct runs.
What ships with it
1 file 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.
- 3d ago First seen · 256 lines · 71 tokens per session scan A b4be86e9ad12
execute-spec is a skill published in the GitHub repository nicknisi/ideation (12 stars, last pushed 6d ago), licensed MIT. It adds 71 tokens to every session and 4,729 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
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…