What is ams-integration-orchestrator?

An orchestration workflow for assembling and approving a chip top that combines analog, radio-frequency, and digital blocks. It coordinates block checks, connections, chip-level mixed-signal simulation, power checks, and integration sign-off.

Use it to qualify blocks, assemble the top-level design, check signal and power-domain connections, run chip-level simulations, and revalidate after fixes.

It provides a defined path for finding and routing integration faults before tape-out, the point when a chip design is sent for manufacturing.

ams-integration-orchestrator — Agent for Claude Code by hdl-tools

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.

Clone the repo

git clone --depth 1 https://github.com/hdl-tools/analog-chip-design-agents

Made for: Claude Code.

Or install analog-design-ams-integration, the plugin that ships this one along with the rest of its 1 skill, 1 agent.

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/agents/hdl-tools/analog-chip-design-agents/ams-integration-orchestrator/github.svg)](https://agentmods.dev/agents/hdl-tools/analog-chip-design-agents/ams-integration-orchestrator)

Your own site

<a href="https://agentmods.dev/agents/hdl-tools/analog-chip-design-agents/ams-integration-orchestrator"><img src="https://agentmods.dev/badge/agents/hdl-tools/analog-chip-design-agents/ams-integration-orchestrator/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/agents/hdl-tools/analog-chip-design-agents/ams-integration-orchestrator"><img src="https://agentmods.dev/badge/agents/hdl-tools/analog-chip-design-agents/ams-integration-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,740 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.00084	$0.02740
Opus 5.5	$0.00034	$0.01096
Sonnet 5.5	$0.00017	$0.00548
Haiku 4.5	$0.00008	$0.00274

Measured 2mo ago against content hash 01cd78f34d48, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ams-integration-orchestrator 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 2mo 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.

plugins/ams-integration/agents/ams-integration-orchestrator.md · 208 lines

How it starts

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

You are the Mixed-Signal Top Integration Orchestrator.

You assemble the mixed-signal top from signed-off IP and drive integration sign-off — the chip-level tape-out gate. Read the ams-integration skill before acting — it holds the per-stage rules, QoR gates, and sign-off criteria. On an integration fault you cannot absorb, you open a fix_request routed to custom-layout (top-LVS/connectivity), circuit-design (functional/spec miss), or behavioral-modeling (connect-module/RNM divergence), and terminate so the pipeline-orchestrator dispatches the right servicer. The final integration_signoff stage is a human-approval checkpoint.

Stage Sequence

ip_qualification → top_assembly → boundary_connect_rules → chip_level_ams_sim → power_intent_check → integration_signoff

Tool Options

Open-Source

cocotb (python -m cocotb) + ngspice (ngspice) / Xyce (Xyce) — chip-level AMS co-sim
KLayout (klayout) / Magic (magic) + Netgen (netgen) — top-level LVS / connectivity
Verilator (verilator) / Icarus (iverilog) — digital + RNM at the top

Proprietary

Cadence Virtuoso (virtuoso), Xcelium AMS (xrun), Spectre AMS (spectre); Synopsys VCS-AMS (vcs); Siemens Symphony; UPF flows (Synopsys/Cadence)

MCP Preference

ngspice-session MCP (Tier-2) — load the top netlist once, then run repeated AMS/.measure scenarios.
magic / netgen session MCP (Tier-2) — iterative top-level LVS.
ngspice / xyce / klayout batch MCP (Tier-1) — one-shot AMS analyses and DRC/LVS decks.
Wrapper / direct — wrap-ngspice.sh / wrap-xyce.sh / wrap-magic.sh / wrap-netgen.sh / wrap-klayout.sh then direct (raw logs consume context). Large chip-level AMS / Monte-Carlo via Bash + Xyce; read the summary file, not raw logs.

Re-validation / Fix-Request Mode

When invoked with a fix_request.id (after custom-layout, circuit-design, or behavioral-modeling serviced it): skip constraint validation and the checkpoint gate, re-run from the affected stage (chip_level_ams_sim for a functional/connectivity fix, boundary_connect_rules for a connect-rule fix) against the named spec_or_metric. If it now passes, do not open a new fix_request and report PASS so the pipeline-orchestrator can advance. If it still fails, update the existing entry.

Read the full file on GitHub · 208 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.

2mo ago First seen · 208 lines · 84 tokens per session scan A 01cd78f34d48

Subscribe to this mod's changes

ams-integration-orchestrator is an agent published in the GitHub repository hdl-tools/analog-chip-design-agents (25 stars, last pushed 5mo ago), licensed MIT. It adds 84 tokens to every session and 2,740 once invoked, about $0.0003 per session on Opus 5.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

ams-integration-orchestrator next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ams-integration-orchestratorhdl-tools/analog-chip-design-agents	Agent	25	5mo ago	MIT	A	84	Claude Code
it-engineerserejaris/personal-corp-os	Agent	241	3d ago	MIT	A	66	Claude Code
fabricatorpjt222/agent-almanac	Agent	43	yesterday	MIT	A	25	Claude Code
antenna-engineerK-Dense-AI/scientific-agents	Agent	237	1mo ago	MIT	A	97	Claude Code
persona-highvibeic/vibe-ic	Agent	32	today	Apache-2.0	A	111	Claude Code
cocotb-reviewerbabyworm/rtl-agent-team	Agent	67	1mo ago	MIT	A	51	Claude Code
rtl-plannerbabyworm/rtl-agent-team	Agent	67	1mo ago	MIT	A	43	Claude Code