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/chipweaver/veripower/brainstormnpx skills add chipweaver/veripower --skill brainstormgit clone --depth 1 https://github.com/chipweaver/veripowerWrote 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/chipweaver/veripower/brainstorm)<a href="https://agentmods.dev/skills/chipweaver/veripower/brainstorm"><img src="https://agentmods.dev/badge/skills/chipweaver/veripower/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 | $0.00039 | $0.01248 |
| Opus 5 | $0.00019 | $0.00624 |
| Sonnet 5 | $0.00008 | $0.00250 |
| Haiku 4.5 | $0.00004 | $0.00125 |
Grade A, and why
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 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Pipeline Requirements Brainstorm
Own the interactive D0–D7 brainstorm dialogue and produce a frozen
{module}/brainstorm.md. Run in your own session, before the design
pipeline: the brainstorm conversation never enters the pipeline's context. The pipeline
starts when the user starts it and reads that file solely inside its sub-agent contexts
(it is the pipeline's input, not a pipeline stage).
When to Use
- A new module needs its requirements + architecture settled before the pipeline.
- A requirements contradiction surfaced downstream and was escalated for revision: the user aborts, re-invokes this skill in revision mode, re-approves.
Iron Rule
- You are pre-pipeline: write exactly one artifact,
{module}/brainstorm.md(creating{module}if absent, before the module enters the pipeline). Write noresult.json, and you are not a pipeline stage — you run before any pipeline state exists. - Do not author design.md / RTL / constraints / any downstream artifact. Your
output is the brainstorm only;
design.mdis derived from it downstream. brainstorm.mdis frozen for the duration of a run. A requirements change is handled by re-invoking this skill in revision mode, never by editing an in-flight artifact to absorb the change: every proof downstream records the fingerprint it read.
Input Artifacts
| Variable / input | Purpose |
|---|---|
{module} |
The module's directory — the same path the pipeline is later given as --module, and where its whole work tree goes. Anywhere the user wants: ~/chips/mydesign, ./mychip, asic/mychip. Its last component is the module name, which titles the brainstorm. |
| User-provided material (optional) | Public spec / reference docs the user pastes or points to. |
No fixed external inputs. Revision mode additionally reads the existing
{module}/brainstorm.md.
Ask for the directory if the user named only a module. Do not invent a parent for them: nothing downstream imposes one, and a guess sends them looking for a tree they did not ask for.
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 · 115 lines · 39 tokens per session scan A e495c8638c42
brainstorm is a skill published in the GitHub repository chipweaver/veripower (4 stars, last pushed 4d ago), licensed MIT. It adds 39 tokens to every session and 1,248 once invoked, about $0.0002 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
vdesign
Generate a design proposal, documentation, and RTL backbone from a requirement file.
varch
Decompose an IP requirement into submodules, define interfaces, and generate an architecture document plus per-module requirement files and a top-level skeleton.
vfill
Implement Verilog code from an approved design proposal, then lint and simulate.
vflow
Scan project state to determine phase completion, write flowstatus.md, and orchestrate the full RTL design flow from architecture to documentation.
vsynth
Synthesize a Verilog module or full IP with Vivado and report resource utilization, Fmax, and power.
vexplain
Generate documentation for any RTL module from Verilog source files.