Borrowing it
Nothing to install: this file belongs to huifer/zeus. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/huifer/zeus/main/.claude/skills/zeus-brainstorm/SKILL.mdgit clone --depth 1 https://github.com/huifer/zeusWrote 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/huifer/zeus/zeus-brainstorm)<a href="https://agentmods.dev/skills/huifer/zeus/zeus-brainstorm"><img src="https://agentmods.dev/badge/skills/huifer/zeus/zeus-brainstorm.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.00065 | $0.00866 |
| Opus 5 | $0.00032 | $0.00433 |
| Sonnet 5 | $0.00013 | $0.00173 |
| Haiku 4.5 | $0.00006 | $0.00087 |
Grade A, and why
zeus-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 8d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zeus Brainstorm - Design-First Planning Loop
Use this skill to transform broad requests into approved design specs before implementation.
Guardrails
- Never skip design, even for "small" features.
- Ask exactly one clarifying question at a time.
- Propose 2-3 options before selecting final architecture.
- Require explicit user approval before planning artifacts are generated.
Preconditions
.zeus/main/config.jsonexists and is valid.- Target version folder exists (
mainby default, optionalvN). - You can read prior artifacts (
prd,task,roadmap,specs,ai-logs).
Context intake
Read first:
.zeus/{version}/config.json.zeus/{version}/prd.json.zeus/{version}/task.json.zeus/{version}/roadmap.json.zeus/{version}/specs/*(recent entries).zeus/{version}/existing-modules.json(if present).zeus/{version}/architecture.md(if present)
If config is missing, stop and instruct user to run /zeus:init.
Deterministic workflow
1) Silent context exploration
Perform read-only exploration and summarize current baseline:
- existing stories/tasks that overlap this request,
- known constraints,
- existing architectural boundaries.
- existing modules that can be reused or extended.
2) Scope fit check
Classify request as:
- single feature,
- multi-feature bundle,
- multi-system program.
If too broad, decompose into independent design tracks and ask user which track to start with.
3) Clarifying question loop
Ask one question per turn. Focus on:
- success criteria,
- constraints,
- user roles,
- non-goals.
Prefer multiple-choice when practical.
4) Approach options (2-3)
Present options with trade-offs and recommendation tied to north_star impact.
For brownfield projects, each option must explicitly classify implementation strategy:
- Reuse existing module
- Extend existing module
- Rewrite with migration plan
5) Section-by-section design review
Present and confirm each section before moving on:
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.
- 8d ago First seen · 148 lines · 65 tokens per session scan A aaeab0ece9eb
zeus-brainstorm is a skill published in the GitHub repository huifer/zeus (22 stars, last pushed 5mo ago), licensed MIT. It adds 65 tokens to every session and 866 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-30.
Other skills, from other repositories
web-static
Build modern static websites using semantic HTML and CSS without external dependencies or build systems. Also owns the verification loop for such sites — drives the rendered pages through Chrome DevTools MCP (console, accessibility snapshot, viewport resize, dark/reduced-motion emulation, Lighthouse), executes the…
web-performance-reviewer
Review web frontends for performance issues by driving the rendered site through Chrome DevTools MCP — throttled performance traces, Core Web Vitals judged against thresholds, network waterfall analysis, and heap-snapshot leak checks for SPAs. Composes on top of web-static, web-sprinkles, or web-components. Strictly…
zcfg
Integrate zcfg (Zero Dependency Configuration Utility) into Java applications. Use when adding configuration loading, reading properties files, setting up application configuration, or integrating zcfg into a Java project. Triggers on "zcfg", "add configuration", "load properties", "application configuration with…
zcl
Add colored terminal output to Java applications using zcl (Zero-dependency Colour Logger). Use when adding colored console output, terminal logging with colors, ANSI color support, or integrating zcl into a Java project. Triggers on "zcl", "colored output", "colored logging", "terminal colors", "ANSI colors"…
zargs
Add zero-dependency argument parsing to Java CLI applications using the zargs pattern — an enum-based argument parser. Use when adding CLI argument parsing, command-line option handling, or adding options to a Java project. Triggers on "zargs", "argument parsing", "CLI arguments", "command-line options", "parse…
zunit
Generate and run zunit tests for java-cli-app projects. Use when asked to create tests, write tests, add tests, or generate test files for a java-cli-app project. Triggers on "zunit", "write tests", "create tests", "add tests", "test this", "generate tests", or requests to test a java-cli-app application. Also trigger…