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 zstevovich/claude-apd --skill apd-brainstormgit clone --depth 1 https://github.com/zstevovich/claude-apdWrote 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/zstevovich/claude-apd/apd-brainstorm)<a href="https://agentmods.dev/skills/zstevovich/claude-apd/apd-brainstorm"><img src="https://agentmods.dev/badge/skills/zstevovich/claude-apd/apd-brainstorm/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/zstevovich/claude-apd/apd-brainstorm"><img src="https://agentmods.dev/badge/skills/zstevovich/claude-apd/apd-brainstorm.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.00183 | $0.01371 |
| Opus 5 | $0.00092 | $0.00685 |
| Sonnet 5 | $0.00037 | $0.00274 |
| Haiku 4.5 | $0.00018 | $0.00137 |
Grade A, and why
apd-brainstorm 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 10d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
APD Brainstorm (Codex)
Finish the question / option / design-approval flow BEFORE calling
apd:apd_advance_pipeline('spec', ...). That call is the only valid exit
after the user explicitly approves the design summary.
When to use / When to skip
Use when:
- The task is vague, broad, or "improve X" style
- The user gave a destination but no path ("we need user search")
- Multiple reasonable interpretations exist
- You catch yourself making implementation choices the user hasn't seen
Skip when:
- The task is fully specified or the user approved a design informally — a genuine 1:1 mirror of a just-completed task, a single-line bug fix, a hotfix with pre-aligned design
- Mid-pipeline (spec locked; raise concerns, don't re-brainstorm)
Skipping this skill does NOT skip the pipeline contract: apd-pipeline-guide
is mandatory on every task regardless, and the spec gate enforces its marker.
This skill answers "WHAT are we building?"; the guide answers "HOW does the
pipeline run?". Only the first question is ever optional.
The Iron Law
NO SPEC WITHOUT SHARED UNDERSTANDING FIRST
If you cannot explain the design in one sentence, you are not ready for a spec-card.md. A vague spec produces vague code.
Process
-
Read project context —
AGENTS.md,.apd/memory/MEMORY.mdand.apd/memory/status.md, source close to the idea. -
Ask ONE question at a time. Never dump a list of 5 questions. Ask one, wait for the answer, ask the next.
-
Present trade-offs, do not decide. When real choices exist, offer 2–3 concise options and let the user pick.
-
Converge on a design. Hand the user a short summary covering Goal / Scope / Out of scope / Approach / Affected files / Regression surface (what this touches INDIRECTLY that must not break; 'none — reason' if self-contained) / Risks / Rollback / Mode / R-criteria / Human gate.
Write the regression surface in the shape the gate parses — one
- RS<N>: <behaviour> — **Cover:** <existing suite | new test | none: reason>per item, plus**Evidence:**per item when Human gate is YES. Agreeing on the content but writing it free-form still fails at the builder advance; the full contract is inapd-pipeline-guide. Wait for explicit approval.
What ships with it
4 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.
- 10d ago First seen · 105 lines · 183 tokens per session scan A 62cb554dfab7
apd-brainstorm is a skill published in the GitHub repository zstevovich/claude-apd (5 stars, last pushed 1mo ago), licensed MIT. It adds 183 tokens to every session and 1,371 once invoked, about $0.0009 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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…