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 chipweaver/veripower --skill simulation-plangit 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/simulation-plan)<a href="https://agentmods.dev/skills/chipweaver/veripower/simulation-plan"><img src="https://agentmods.dev/badge/skills/chipweaver/veripower/simulation-plan/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/chipweaver/veripower/simulation-plan"><img src="https://agentmods.dev/badge/skills/chipweaver/veripower/simulation-plan.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.00035 | $0.00950 |
| Opus 5.5 | $0.00014 | $0.00380 |
| Sonnet 5.5 | $0.00007 | $0.00190 |
| Haiku 4.5 | $0.00003 | $0.00095 |
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 1mo 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification Planning
Plan how the task's required behavior and power questions will be verified. Expected behavior comes from the original intent and resolved design choices. Implementation or diagnostic evidence can explain a discrepancy; it does not redefine the requirement being checked.
Write under {workdir}. Read dispatch.json for the input locations: intent is the original
material; design, manifest, clocks, requirements, check_hints and top_io resolve to the
specification directory. Use design.md for behavior, interfaces and timing scenarios, and consult
the original intent when its meaning or a derived requirement is in doubt.
Author or amend the plan
Continue from the artifacts already in {workdir}. Use changed inputs (scope), reported failures
(caused_by) and any supplied decisions (reasons) to determine the work. Their absence does not
mean a first delivery. Preserve unaffected content and identifiers; create missing artifacts as
needed. A diagnosis supplies evidence to examine, not an automatic instruction to change acceptance.
| Artifact | Purpose |
|---|---|
verification-plan.md |
Strategy, power measurement meaning and material decisions; use the outline |
tb-scaffold.json |
Functional agents, tests, testpoints, reference-model/scoreboard organization and skipped checks |
sequences.json |
Functional sequences implemented by simulation |
power-scenarios.json |
Identifiers for the power measurements explained in the plan |
The sidecar formats are tb-scaffold.schema.json, sequences.schema.json and power-scenarios.schema.json. spec-input-contract.md explains how the specification feeds the functional scaffold and sequence reuse.
Account for each check-hints.json check in testpoints[].covers[] or a justified skipped_checks[]
entry. Assess disputed expectations and reachability against the original requirement and technical
evidence. Correct mistaken testpoints and report implementation defects to their owner. Record
material scope decisions in the plan.
What ships with it
14 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 1.3 KB
- references/power-scenarios-template.md 729 B
- references/power-scenarios.schema.json 774 B
- references/result.schema.json 1.2 KB
- references/sequences.schema.json 920 B
- references/spec-input-contract.md 2.5 KB
- references/tb-scaffold.schema.json 6.0 KB
- references/verification-plan-template.md 846 B
- scripts/simplan/__init__.py 0 B runs code
- scripts/simplan/__main__.py 2.6 KB runs code
- scripts/simplan/hints.py 1.6 KB runs code
- scripts/simplan/plan.py 3.0 KB runs code
- scripts/simplan/result.py 2.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.
- 1mo ago Changed · -78 lines · -3 tokens per session ca13f32ecf83
- 1mo ago Changed · -4 lines 0d1f78d80926
- 1mo ago Changed c8a0a0fd6103
- 1mo ago Changed c43953b0ee32
- 1mo ago Changed · +1 lines 4083e6b56faf
- 1mo ago First seen · 163 lines · 38 tokens per session scan A dba388dfc884
simulation-plan is a skill published in the GitHub repository chipweaver/veripower (10 stars, last pushed 7d ago), licensed MIT. It adds 35 tokens to every session and 950 once invoked, about $0.0001 per session on Opus 5.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.