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/simra-tech/openada/bootstrap-asic-projectnpx skills add simra-tech/OpenADA --skill bootstrap-asic-projectgit clone --depth 1 https://github.com/simra-tech/OpenADAWhat 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.00111 | $0.02871 |
| Opus 5 | $0.00056 | $0.01435 |
| Sonnet 5 | $0.00022 | $0.00574 |
| Haiku 4.5 | $0.00011 | $0.00287 |
Grade A, and why
bootstrap-asic-project 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.
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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bootstrap ASIC Project
Turn an underspecified chip idea into a frozen project context and a sequence of
honest engineering gates. Use $openada:openada for every implemented OpenADA
assertion. Keep provisioning, design creation, native gap work, and foundry
acceptance distinct from OpenADA-normalized evidence.
Define the finish line first
Record the intended deliverable before installing or generating anything:
core: synthesized or routed hard macro without package-facing IO;full-chip candidate: core plus IO/ESD cells, power pads, bondpads, pad ring, seal ring, fill/density, final GDS and reference netlist; orsubmission candidate: a full-chip candidate checked against the current shuttle checklist and ready for the foundry's intake review.
Also record the function, interfaces, clock, reset, voltage domains, die or area limit, package/bonding assumption, license constraint, target shuttle, and required verification. Do not let “CPU” silently mean only synthesizable RTL. If the user authorizes autonomous choice, choose the smallest target consistent with these constraints and document the decision. Otherwise ask one choice that materially changes the process or padframe.
Inspect in the safe order
- Establish one writable project root and a separate evidence root. Treat PDK, official template, and shared source checkouts as read-only.
- Resolve the OpenADA CLI exactly as
$openada:openadaspecifies. Record the plugin and CLI versions separately; a plugin marketplace installation does not install the Python entry point or EDA products. - Check free disk, memory, architecture, container/Nix availability, and an already-present compatible runtime before downloading tools. Prefer a pinned compatible runtime already on the machine over unrelated “latest” binaries.
- Run
openada capabilities, then one scoped preflight for only the smallest next implemented assertion. A preflight pass is tool readiness, not a design result. - Read configured PDK roots and explicit project context. Do not recursively crawl the host or a PDK tree to compensate for an empty catalog. Do not infer that an empty preflight PDK list means no PDK exists.
What ships with it
4 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.
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.
- 2d ago First seen · 220 lines · 111 tokens per session scan A e359eaf23119
bootstrap-asic-project is a skill published in the GitHub repository simra-tech/OpenADA (24 stars, last pushed 20d ago), licensed MIT. It adds 111 tokens to every session and 2,871 once invoked, about $0.0006 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.
Other skills, from other repositories
tia-multiuser
TIA Portal Multiuser Engineering operations. Use for managing server projects, local sessions, and multiuser commissioning workflows.
embedded-project-loop
Use first when Arduino or embedded hardware work spans sessions, parts delivery, wiring, soldering, flashing, measurements, field tests, recovery, or a durable next-todo is needed. Maintain explicit evidence and concrete physical-world user gates instead of assuming completion.
hardware-team
Hardware delivery team with 8-stage pipeline orchestrator for structured hardware product development. Coordinates 6 hardware roles (HW Product Owner, Electrical Engineer, PCB Layout Engineer, Manufacturing Engineer, Compliance Engineer, Test Engineer) through concept-to-production pipeline. Consumes kicad-happy…
iot-ai-tasks
Natural-language task lifecycle and authoritative backend routing with validation, WIP control, evidence, audit and Founder handoff.
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.