chipforge

An FPGA design toolkit for writing and checking Verilog, a language used to describe digital circuits, then simulating how those circuits behave.

In plain words
What is it for?
It helps create Verilog modules and testbenches, check syntax, run simulations, inspect VCD waveform files, and record connections and signal examples in a project knowledge graph.
Why use it?
It guides the work from code creation through compilation, simulation, waveform review, and documentation, helping find design errors before hardware testing.

Skill for Claude CodeCodex

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/fzhiyu1/chipforge-plugin/chipforge
Any agent
npx skills add Fzhiyu1/chipforge-plugin --skill chipforge
Clone the repo
git clone --depth 1 https://github.com/Fzhiyu1/chipforge-plugin

Made for: Claude Code, Codex.

Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,053 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.00046 $0.02053
Opus 5 $0.00023 $0.01026
Sonnet 5 $0.00009 $0.00411
Haiku 4.5 $0.00005 $0.00205

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

Security

Grade A, and why

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

The scan reads SKILL.md. This mod also ships 2 executable files (bin/iverilog.bat, bin/vvp.bat), 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/chipforge/SKILL.md · 233 lines

How it starts

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

ChipForge AI

AI-powered FPGA development toolkit for Verilog simulation and design analysis.


FPGA Development Workflow (MUST FOLLOW)

When user requests to design/implement a Verilog module, follow this workflow:

Phase 1: Knowledge Graph Setup

  1. Initialize knowledge graph: chipforge-kg.exe init <project>
  2. Add module nodes with properties (Signal type)
  3. Add state machine nodes if applicable (StateTransition type)
  4. Add relations between modules (RELATED, STATETRANSITION)

Phase 2: Implementation

  1. Create project directory structure: rtl/, tb/
  2. Write RTL code in rtl/ directory
  3. Write testbench in tb/ directory (include $dumpfile and $dumpvars)

Phase 3: Verification Loop

  1. Syntax check → Fix errors if any
  2. Compile → Fix errors if any
  3. Simulate → Generate VCD
  4. Analyze VCD → Check waveforms
  5. Fix issues → Repeat from step 8 if needed

Phase 4: Documentation

  1. Add simulation results to knowledge graph (SignalExample type)
  2. Link results to modules (EXAMPLES relation)
  3. Report final status to user

Workflow Diagram

[Init KG] → [Write Code] → [Syntax Check]
                                ↓
                [Fix Code] ← [Errors?]
                    ↓            ↓ No
                   Yes      [Compile]
                    ↑            ↓
                [Fix Code] ← [Errors?]
                                ↓ No
                           [Simulate]
                                ↓
                          [Analyze VCD]
                                ↓
                [Fix Code] ← [Issues?]
                                ↓ No
                         [Update KG] → [Done]

IMPORTANT Rules

  • NEVER skip syntax check before simulation
  • ALWAYS generate VCD in testbench ($dumpfile, $dumpvars)
  • ALWAYS analyze VCD after simulation
  • ALWAYS update knowledge graph with results

Available Tools (ONLY use these, do NOT guess other tool names)

Tool Purpose
iverilog.exe Verilog compiler
vvp.exe Simulation runtime
vcd2wavedrom.exe VCD to WaveJSON converter
chipforge-kg.exe Knowledge graph CLI

Read the full file on GitHub · 233 lines

Files

What ships with it

60 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. 2d ago First seen · 233 lines · 46 tokens per session scan A 64ed550dc8fd

Subscribe to this mod's changes

chipforge is a skill published in the GitHub repository Fzhiyu1/chipforge-plugin (4 stars, last pushed 7mo ago), licensed MIT. It adds 46 tokens to every session and 2,053 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens