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 oliver-kriska/claude-elixir-phoenix --skill phx-brainstormgit clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenixWrote 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/oliver-kriska/claude-elixir-phoenix/phx-brainstorm)<a href="https://agentmods.dev/skills/oliver-kriska/claude-elixir-phoenix/phx-brainstorm"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/phx-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/oliver-kriska/claude-elixir-phoenix/phx-brainstorm"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/phx-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.00042 | $0.01428 |
| Opus 5 | $0.00021 | $0.00714 |
| Sonnet 5 | $0.00008 | $0.00286 |
| Haiku 4.5 | $0.00004 | $0.00143 |
Grade A, and why
phx-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 6d 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.
This is a copy
86% identical to brainstorm — 38 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm — Adaptive Requirements Gathering
Interactive interview → research → synthesis loop. Produces structured
interview.md that phx-plan detects and consumes (skipping clarification).
Usage
phx-brainstorm Add some kind of notification system
phx-brainstorm Improve authentication security
phx-brainstorm # starts with open question
Workflow
phx-brainstorm {topic}
|
v
[INTERVIEW] ←──────────────────┐
| |
v (sufficient OR user exit) |
[DECISION POINT] |
├─ Research ──→ [RESEARCH] ─┘
├─ Continue interview ──────┘
├─ Make a plan ──→ STOP (suggest phx-plan {slug})
├─ Store & exit ──→ STOP (artifacts saved)
└─ Discuss ──→ freeform ──→ [DECISION POINT]
Phase 1: Adaptive Interview
Create .claude/plans/{slug}/ directory. Start asking ONE question at a time.
Coverage Dimensions
Track coverage across 6 dimensions (0=uncovered, 1=partial, 2=sufficient). Ask Scope early — for "optimize X" topics, ask about boundaries (upstream OK? Local-only? CI vs dev?) before research, not during.
| Dim | Target | Sufficient signal |
|---|---|---|
| What | Specific behavior/features | Concrete verbs, not "some kind of" |
| Why | Problem solved, user need | Clear benefit stated |
| Scope | In/out boundaries | Explicit exclusions stated |
| Where | Modules, contexts, pages | File paths or context names mentioned |
| How | Approach, constraints | At least one concrete constraint |
| Edge | Error states, scale, auth | 2+ edge cases identified |
Interview is "sufficient" when total score >= 8 out of 12.
Context-Aware Questioning
Before each question, run a brief codebase scan on topics the user mentioned:
- User mentions a topic (e.g., "notifications") → run Grep/Glob for related patterns
- Use scan results to ground your next question in what actually exists
- Unknown/niche topic → suggest research pause before continuing
What ships with it
2 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.
- 6d ago First seen · 148 lines · 42 tokens per session scan A f8ea5de5e06a
phx-brainstorm is a skill published in the GitHub repository oliver-kriska/claude-elixir-phoenix (542 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 1,428 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to brainstorm, differing in 38 lines, and is treated as a copy.
Other skills, from other repositories
craftcms
Craft CMS 5 plugin and module development — extending Craft with PHP. Covers elements, element queries, services, models, records, controllers, migrations, queue jobs, console commands, field types, native fields, events, behaviors, Twig extensions, widgets, filesystems, permissions, project config, GraphQL, testing…
craft-twig-guidelines
Twig coding standards and conventions for Craft CMS 5 templates. ALWAYS load this skill when writing, editing, or reviewing any .twig file in a Craft CMS project — even for small edits. Covers: variable naming (camelCase, no abbreviations), null handling (?? operator, ??? with empty-coalesce plugin), whitespace…
craft-pest
Testing Craft CMS 5 plugins and modules with Pest — test isolation, database safety, and the markhuot/craft-pest-core harness. ALWAYS load when writing, running, fixing, or reviewing tests for a Craft plugin or module, and whenever a suite touches a real Craft install. Covers why rollback is opt-in, tests/Pest.php +…
craft-plugin-release
Releasing Craft CMS plugins — tagging, Packagist propagation, GitHub releases, branch promotion, shared-library ordering, history rewrites. ALWAYS load when cutting, preparing, verifying, or debugging a plugin release: bumping a version, dating a changelog, creating or moving a git tag, or checking what Packagist…
craft-cloud
Craft Cloud — Pixel & Tonic's serverless hosting platform for Craft CMS. Covers craft-cloud.yaml configuration, the Build → Migrate → Release deploy pipeline, the craftcms/cloud extension package, edge image transforms via Cloudflare, edge static caching with cache.rules + ESI, Cloud-managed S3 filesystem, MySQL 8 /…
craft-site
Craft CMS 5 front-end Twig development — atomic design, template architecture, components, Vite buildchain. Covers atoms/molecules/organisms, props/extends/block patterns, layout chains, view routing, content builders, image presets, Tailwind named-key collections, multi-brand CSS tokens, JavaScript boundaries…