What is vibe-ic-phase23?

A command that runs the second and third phases of a hardware design workflow in sequence. It covers checks and FPGA steps in phase two, then chip layout and verification in phase three.

Use it to run the complete phase-two and phase-three process for a specified project directory and produce a combined JSON report.

It automates the handoff between phases and stops before phase three when phase two fails.

vibe-ic-phase23 — Command for Claude Code by vibeic

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add vibeic/vibe-ic

Claude Code

/plugin install vibe-ic

Made for: Claude Code.

Or install vibe-ic, the plugin that ships this one along with the rest of its 70 skills, 8 commands, 8 agents, 2 hooks, 1 MCP server.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/vibeic/vibe-ic/vibe-ic-phase23/github.svg)](https://agentmods.dev/commands/vibeic/vibe-ic/vibe-ic-phase23)

Your own site

<a href="https://agentmods.dev/commands/vibeic/vibe-ic/vibe-ic-phase23"><img src="https://agentmods.dev/badge/commands/vibeic/vibe-ic/vibe-ic-phase23/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/vibeic/vibe-ic/vibe-ic-phase23"><img src="https://agentmods.dev/badge/commands/vibeic/vibe-ic/vibe-ic-phase23.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 64 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 894 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00064	$0.00894
Opus 5	$0.00032	$0.00447
Sonnet 5	$0.00013	$0.00179
Haiku 4.5	$0.00006	$0.00089

Measured 10d ago against content hash 52076daba450, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

vibe-ic-phase23 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 10d 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.

vibe-ic-marketplace/plugins/vibe-ic/commands/vibe-ic-phase23.md · 46 lines

How it starts

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

Missing arg? When $ARGUMENTS is empty, prompt the user first: /vibe-ic-phase23 <project-dir> (e.g. /vibe-ic-phase23 1st_benchmark_example/phase2_v0119.48-vendor). The AI must NOT guess the path; a concrete project path is required before continuing.

/vibe-ic-phase23 — Phase 2 + Phase 3 true chain

Main execution (program-driven):

python3 ${CLAUDE_PLUGIN_ROOT}/programs/phase23_one_shot_runner.py $ARGUMENTS

This runner is a thin-shell chain:

Delegates to design_one_shot_runner.py to run Phase 2 (rig_topology skeleton → phase1 → rtl_gen → reference_tb → yosys → qsf/sdc → otp_check → fpga compile/burn → → manifests → final_audit @phase 2)
If Phase 2 verdict==FAIL, auto-halt without entering Phase 3 (unless --skip-phase3 is the user-specified alias usage)
Phase 2 PASS / PASS_WITH_WAIVERS → delegates to phase3_one_shot_runner.py to run Phase 3 (synth/PnR/GDS/DRC/LVS)
Aggregates JSON reports from both phases → <project>/reports/phase23_one_shot.json

After the run completes, the AI must (combine /vibe-ic-phase2 + /vibe-ic-phase3 monitoring rules):

Read <project>/reports/phase23_one_shot.json — inspect phase2.verdict / phase3.verdict / overall verdict
Phase 2 FAIL → close-loop per /vibe-ic-phase2 rules; Phase 3 FAIL → per /vibe-ic-phase3 rules
Acceptance gate (per CLAUDE.md SOLE ACCEPTANCE CRITERION):
- Overall: PASS — production tapeout-ready
- Overall: PASS_WITH_WAIVERS — every deferred step in waivers.json must carry evidence + ticket id + review_required: true
- Overall: FAIL — not complete, keep working
Individual gate PASS does NOT mean Phase 2+3 is complete

Flag mapping:

--skip-phase3 ≡ exactly equivalent to /vibe-ic-phase2
--skip-phase2 ≡ exactly equivalent to /vibe-ic-phase3 (precondition: rtl/ + generated_docs/ already prepared)

Helper skills: same as /vibe-ic-phase2 + /vibe-ic-phase3, plus tapeout-checklist, flow-orchestrate.

Read the full file on GitHub · 46 lines

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.

10d ago First seen · 46 lines · 64 tokens per session scan A 52076daba450

Subscribe to this mod's changes

vibe-ic-phase23 is a command published in the GitHub repository vibeic/vibe-ic (23 stars, last pushed today), licensed Apache-2.0. It adds 64 tokens to every session and 894 once invoked, about $0.0003 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-30.

Hardware and IoT ai-agents asic claude eda ic-design mcp

pcb-new

Start a new PCB project from a text description. Sources parts, generates a wired .kicadpcb, and hands off to EasyEDA for routing + JLCPCB ordering.

BeckhamLabsLLC/kicad-jlcpcb · 40 tokens

pcb-from-bom

Start a PCB project from an existing LCSC BOM file (CSV with C-numbers) and a design-intent description.

BeckhamLabsLLC/kicad-jlcpcb · 30 tokens

eol-report

EOL/EOS risk report — devices, OS versions, and firmware approaching or past end-of-life/end-of-support, prioritized by criticality.

WYRE-AI/msp-claude-plugins · 28 tokens

pentest-wireless

You are an expert wireless security tester covering Wi-Fi, Bluetooth, and IoT radio protocols. For AUTHORIZED testing only.

JoasASantos/ClaudeAdvancedPlugins · 0 tokens

hw-troubleshoot

A hardware diagnostic command that scans for I²C devices, checks power, and analyzes signal quality. I²C is a short-distance communication bus used by many sensors and chips.

phinn/KinetAios · 34 tokens

arckit.eu-data-act

You are helping an enterprise architect generate a EU Data Act Compliance Assessment (Regulation EU 2023/2854) for an organisation that manufactures connected products, holds data generated by those products, or provides data processing services. Most Data Act obligations apply from 12 September 2025.

tractorjuice/arckit-codex · 31 tokens