timing-analysis

timing-analysis is a skill for Claude Code, Codex from chipweaver/veripower. It costs 41 tokens per session (1,435 once invoked), scanned A, original, MIT.

A static timing-analysis skill for digital hardware. It runs PrimeTime on the circuit produced after synthesis and checks whether signals arrive on time, including setup and hold requirements.

In plain words
What is it for?
Use it to analyze timing reports, classify setup and hold violations, and recheck timing after synthesis changes.
Why use it?
It independently verifies timing after synthesis instead of relying only on the synthesis tool's timing results.

Skill for Claude CodeCodex

Part of the veripower plugin — 12 skills, 3 hooks shipped together

Install

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.

agentmods
npx agentmods add skills/chipweaver/veripower/timing-analysis
Any agent
npx skills add chipweaver/veripower --skill timing-analysis
Clone the repo
git clone --depth 1 https://github.com/chipweaver/veripower

Made for: Claude Code, Codex.

Or install veripower, the plugin that ships this one along with the rest of its 12 skills, 3 hooks.

Wrote 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.

agentmods badge for timing-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/chipweaver/veripower/timing-analysis.svg)](https://agentmods.dev/skills/chipweaver/veripower/timing-analysis)
Your own site
<a href="https://agentmods.dev/skills/chipweaver/veripower/timing-analysis"><img src="https://agentmods.dev/badge/skills/chipweaver/veripower/timing-analysis.svg" alt="Measured on agentmods" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,435 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00041 $0.01435
Opus 5 $0.00020 $0.00718
Sonnet 5 $0.00008 $0.00287
Haiku 4.5 $0.00004 $0.00144

Measured 3d ago against content hash 516369fd5f64, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

timing-analysis 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.

The scan reads SKILL.md. This mod also ships 4 executable files (scripts/timing/__init__.py, scripts/timing/__main__.py, scripts/timing/bootstrap.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/timing-analysis/SKILL.md · 119 lines

How it starts

The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Static Timing Analysis

Your sole responsibility: run PrimeTime over the post-synthesis netlist, independently of the timing engine inside synthesis, and close the run through the timing CLI. You never grade setup or hold by eye — finalize classifies both off the report and writes the verdict.

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 produce

<skill> is this skill's own base directory, named on the first line of this file.

{workdir}/dispatch.json carries the inputs table, but you open none of what it points at: bootstrap resolves <TOP> from the single out/<TOP>_syn.v under the synthesis stage root and bakes absolute paths into the TCL, which reads that netlist and the SDC synthesis exported beside it.

The one thing you supply is LIB_DB, the std-cell Liberty .db synthesis linked against.

Everything under {workdir} is produced by the tools you invoke, and finalize enumerates it into artifacts[]: the deployed run_sta.tcl and config.tcl, plus timing-report.txt — the setup, hold and check_timing output that is this stage's deliverable and the only thing the gate reads.

Workflow

1. Deploy

Export LIB_DB, then run bootstrap to lay down the run scaffold:

export LIB_DB=<path-to-slow.db>
python3 <skill>/scripts/timing/__main__.py bootstrap --workdir {workdir}

It deploys run_sta.tcl + config.tcl, resolves <TOP>, verifies the netlist and SDC the TCL reads, and aborts when {workdir} already holds a deployment. pt_shell reads LIB_DB out of the config.tcl written here rather than out of the environment, so exporting it afterwards changes nothing: bootstrap refuses to deploy without it instead of leaving you a workdir whose STA cannot run. Non-zero exit: stderr names the cause, and nothing was deployed, so the retry is not blocked.

Read the full file on GitHub · 119 lines

Files

What ships with it

7 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.

Changes

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.

  1. 3d ago First seen · 119 lines · 41 tokens per session scan A 516369fd5f64

Subscribe to this mod's changes

timing-analysis is a skill published in the GitHub repository chipweaver/veripower (4 stars, last pushed 4d ago), licensed MIT. It adds 41 tokens to every session and 1,435 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.