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/simulation-plannpx skills add chipweaver/veripower --skill simulation-plangit 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.00038 | $0.02262 |
| Opus 5 | $0.00019 | $0.01131 |
| Sonnet 5 | $0.00008 | $0.00452 |
| Haiku 4.5 | $0.00004 | $0.00226 |
Grade A, and why
simulation-plan 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification Planning
Your sole responsibility: from specification, produce verification-plan.md — the human-readable
review anchor — plus its machine half, three sidecars split so each downstream consumer declares
only what it reads.
Iron Rule
- Write only under
{workdir}; never another module's artifacts. - Do not read RTL source, do not invoke EDA tools. A plan written from the implementation verifies the implementation against itself.
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. design / manifest / children /
clocks / features / check_hints / top_io all resolve to the specification stage root.
| Path | What it is |
|---|---|
<design>/design.md |
§1 behavior, §1.4 boundary, and §1.5 timing scenarios with their waveforms — the only home for the scenarios you author sequences from, so you read it |
<children>/<child>.md |
Per-child implementation constraints a testpoint may have to verify: register side effects, exceptions, concurrency, back-pressure, reset, state-machine boundaries |
<design>/features.json |
The feature list you author testpoints and tests from |
<check_hints>/ (per child, one file) |
Per child, the checks that verify it — check_id is unique across all of them |
<design>/clocks.json, <design>/top-io.json |
The clock and the DUT boundary materialize-scaffold derives from |
<manifest>/manifest.json |
.module is the Top field in plan §1; children[] is the roster the check hints are aggregated over |
Everything below is produced under {workdir}.
| Path | What it is |
|---|---|
verification-plan.md |
The review anchor the human gate is held over (template: references/verification-plan-template.md) |
tb-scaffold.json |
What simulation builds the TB from: agents / tests / testpoints[] / rm / scoreboard / skipped_checks[] |
sequences.json |
The sequence roster — the one part both simulation and power-analysis read |
power-scenarios.json |
The power scenarios, read by power-analysis alone. Its own file so a scenario-only edit does not invalidate simulation's proof |
plan-review/review.md, plan-review/decisions.md |
The reviewer's findings, and the user's resolution of anything it called blocking |
result.json |
The status envelope |
What ships with it
15 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/plan-review-task-contract.md 3.6 KB
- references/power-scenarios-template.md 2.0 KB
- references/power-scenarios.schema.json 2.2 KB
- references/result.schema.json 1.5 KB
- references/sequences.schema.json 1.2 KB
- references/spec-input-contract.md 5.7 KB
- references/tb-scaffold.schema.json 9.0 KB
- references/verification-plan-template.md 1.4 KB
- scripts/simplan/__init__.py 0 B runs code
- scripts/simplan/__main__.py 4.3 KB runs code
- scripts/simplan/_plan.py 3.7 KB runs code
- scripts/simplan/hints.py 2.4 KB runs code
- scripts/simplan/materialize.py 7.4 KB runs code
- scripts/simplan/result.py 5.9 KB runs code
- scripts/simplan/scaffold.py 9.6 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 · 163 lines · 38 tokens per session scan A dba388dfc884
simulation-plan is a skill published in the GitHub repository chipweaver/veripower (4 stars, last pushed 3d ago), licensed MIT. It adds 38 tokens to every session and 2,262 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.