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/specificationnpx skills add chipweaver/veripower --skill specificationgit clone --depth 1 https://github.com/chipweaver/veripowerWhat 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.02206 |
| Opus 5 | $0.00019 | $0.01103 |
| Sonnet 5 | $0.00008 | $0.00441 |
| Haiku 4.5 | $0.00004 | $0.00221 |
Grade A, and why
specification 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 2d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements and Specification Freeze
Your sole responsibility: derive a frozen design source of truth from the delivered
<brainstorm>/brainstorm.md. You dispatch and hold no document body: brainstorm.md,
design.md and every <child>.md are read and written only inside sub-Task contexts. The
brainstorm dialogue itself belongs to the pre-pipeline brainstorm skill.
Iron Rule
Write only under {workdir}; never another module's artifacts. Reading templates and upstream inputs outside it is fine.
Artifacts
<skill> is this skill's own base directory, named on the first line of this file.
Read {workdir}/dispatch.json for this round's inputs: its inputs table maps each upstream key to a location, so <key>/<subpath> is how you address one. The only input is <brainstorm>/brainstorm.md (brainstorm is a PIPELINE_INPUT, so <brainstorm> is the module root) — frozen for the run, and read only inside the sub-Tasks that need it.
Everything below is produced under {workdir}. Each JSON sidecar's shape is references/<name>.schema.json.
| Path | What it is |
|---|---|
design.md |
Module overview §1.1–1.6 + §1.7 pointer to the manifest (template: references/design-template.md) |
children/<child>.md × N |
Per-child sub-design (template: references/child-design-template.md); children/ leaves as one tree |
manifest.json |
The child partition: module + children[] (name / doc / rtl_modules[] / brainstorm_anchor) |
clocks.json, top-io.json, interconnects.json |
The boundary: clocks, top-level ports, cut edges |
features.json, check-hints/ |
The feature list, and per child the checks that verify it; check-hints/ leaves as one tree |
ppa.json |
PPA targets, verbatim from brainstorm D6 ([] when none) |
constraints/<TOP>.sdc, constraints/<TOP>.sgdc |
Generated by derive-constraints |
spec-review/ |
Wave-3 reviews and the user's resolution of anything they called blocking; the directory is delivered and endorsed whole |
result.json |
The status envelope |
What ships with it
18 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.
- references/check-hints.schema.json 2.7 KB
- references/child-design-template.md 3.6 KB
- references/clocks.schema.json 1.6 KB
- references/decompose-task-contract.md 2.9 KB
- references/design-template.md 10.0 KB
- references/features.schema.json 2.4 KB
- references/interconnects.schema.json 2.4 KB
- references/ppa.schema.json 921 B
- references/result.schema.json 2.2 KB
- references/spec-review-task-contract.md 3.5 KB
- references/top-io.schema.json 2.9 KB
- scripts/spec/__init__.py 0 B runs code
- scripts/spec/__main__.py 3.9 KB runs code
- scripts/spec/constraints.py 10 KB runs code
- scripts/spec/crossrefs.py 6.5 KB runs code
- scripts/spec/ports.py 4.0 KB runs code
- scripts/spec/result.py 7.2 KB runs code
- scripts/spec/sidecar.py 6.9 KB runs code
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.
- 2d ago First seen · 125 lines · 39 tokens per session scan A f6208998944d
specification is a skill published in the GitHub repository chipweaver/veripower (4 stars, last pushed 3d ago), licensed MIT. It adds 39 tokens to every session and 2,206 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.