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/lint-cdcnpx skills add chipweaver/veripower --skill lint-cdcgit 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/lint-cdc)<a href="https://agentmods.dev/skills/chipweaver/veripower/lint-cdc"><img src="https://agentmods.dev/badge/skills/chipweaver/veripower/lint-cdc.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.00040 | $0.01985 |
| Opus 5 | $0.00020 | $0.00992 |
| Sonnet 5 | $0.00008 | $0.00397 |
| Haiku 4.5 | $0.00004 | $0.00198 |
Grade A, and why
lint-cdc 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 5d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lint / CDC
Your sole responsibility: converge SpyGlass lint and CDC to a clean error and warning count on
this module's RTL, and close the run through the lintcdc CLI.
Iron Rule
- Write only under
{workdir}. Every injected input location is read-only, as is every other stage's output. - Scripts are black boxes, never Read their source. Invoke them per this skill's documented
command lines (flags via
--help); on a non-zero exit act on the documented failure protocol (stderr, stdout verdict), not the source. Sole exception: debugging a suspected bug in a script itself.
What you read, and what you edit
<skill> is this skill's own base directory, named on the first line of this file.
{workdir}/dispatch.json carries the inputs table below, so <key> denotes a location and
you read <key>/<subpath>. It also carries a scope list when the kernel knows which inputs
changed since your last run: that narrows what you triage, never what the tool analyzes.
| Path | Use |
|---|---|
<annotations>/constraint-annotations.json |
The sgdc block per child: every depth annotation this RTL implies. bootstrap renders all four categories into the SGDC itself — you never transcribe them. Nothing upstream matched a name against the netlist, so a name SpyGlass cannot find surfaces here first, as its author's defect. Schema: skills/rtl-design/references/constraint-annotations.schema.json. |
<rtl>/rtl-files.json |
Per-child file layout, which bootstrap turns into scripts/filelist.txt. Schema: skills/rtl-design/references/rtl-files.schema.json. |
<sgdc_seed>/constraints/<TOP>.sgdc |
Clocks and resets from specification. bootstrap reads it every round, so a correction here arrives on its own; it is not yours to restate or override. |
Two files under {workdir} are yours, and both reach you holding the previous round's work
rather than a pristine template:
scripts/local.sgdc: your own SGDC — the port/clock associations the seed cannot know.scripts/waiver.tcl: the waivers, each carrying its reason.
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/attribution-rules.md 3.4 KB
- references/result.schema.json 2.4 KB
- scripts/lintcdc/__init__.py 0 B runs code
- scripts/lintcdc/__main__.py 2.8 KB runs code
- scripts/lintcdc/bootstrap.py 12 KB runs code
- scripts/lintcdc/result.py 10 KB runs code
- templates/env.sh 792 B runs code
- templates/Makefile 2.9 KB
- templates/README.md 1.0 KB
- templates/scripts/collect_report.py 12 KB runs code
- templates/scripts/local.sgdc 1.0 KB
- templates/scripts/run_spyglass.sh 1.2 KB runs code
- templates/scripts/run.tcl 1.9 KB
- templates/scripts/spyglass_lint.prj 1.0 KB
- templates/scripts/waiver.tcl 1.9 KB
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.
- 5d ago First seen · 144 lines · 40 tokens per session scan A 130ba506d9e1
lint-cdc is a skill published in the GitHub repository chipweaver/veripower (6 stars, last pushed 5d ago), licensed MIT. It adds 40 tokens to every session and 1,985 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.