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 skills add hdl-tools/analog-chip-design-agents --skill rf-designgit clone --depth 1 https://github.com/hdl-tools/analog-chip-design-agentsWrote 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.
[](https://agentmods.dev/skills/hdl-tools/analog-chip-design-agents/rf-design)<a href="https://agentmods.dev/skills/hdl-tools/analog-chip-design-agents/rf-design"><img src="https://agentmods.dev/badge/skills/hdl-tools/analog-chip-design-agents/rf-design/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.
<a href="https://agentmods.dev/skills/hdl-tools/analog-chip-design-agents/rf-design"><img src="https://agentmods.dev/badge/skills/hdl-tools/analog-chip-design-agents/rf-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00134 | $0.03644 |
| Opus 5 | $0.00067 | $0.01822 |
| Sonnet 5 | $0.00027 | $0.00729 |
| Haiku 4.5 | $0.00013 | $0.00364 |
Grade A, and why
rf-design 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.
How it starts
The opening of the file, as written. The whole thing — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: RF / mmWave Design
Invocation
- If invoked by a user presenting an RF design task: immediately spawn the
analog-chip-design-agents:rf-design-orchestratoragent and pass the full user request and any available context. Do not execute stages directly. - If invoked by the
rf-design-orchestratormid-flow (including re-validation after a serviced fix_request): do not spawn a new agent. Treat this file as read-only — return the requested stage rules, sign-off criteria, or loop-back guidance.
Spawning the orchestrator from within an active orchestrator run causes recursive delegation and must never happen.
Pre-run Context
Before executing or advising on any stage, read the following if they exist:
memory/rf/knowledge.md— known matching/stability fixes, HB convergence recipes, phase-noise and load-pull patterns, and PDK/tool quirks. Incorporate its guidance into every stage.memory/rf/run_state.md— current run identity for resume-after-interruption.
Purpose
Design and verify an RF/mmWave block — select and match the topology, extract S-parameters, run
harmonic-balance / Pnoise / IP3 / load-pull, and sign off against the RF spec table across the
required corners. Seven stages with explicit QoR gates. RF design is a cross-domain producer —
its loop-backs are stage-local first (spec/stability fail → topology_matching; non-convergence →
harmonic_balance settings); when a stage-local cap is exhausted and the block still misses spec it
opens a cross-domain fix_request. It reads the EM-modeling passive model (Touchstone +
fitted lumped model) from design_state.em as a data dependency; a limiter traced to a passive
opens a fix_request with route_to: em-modeling (an automated EM re-solve), while a device-level
spec miss opens one with route_to: circuit-design. The pipeline-orchestrator re-validates the fix
via this orchestrator.
Supported EDA Tools
Open-Source
- Qucs-S (
qucs-s) — schematic + harmonic-balance front-end (RF capable) - Xyce (
xyce) — parallel SPICE with harmonic balance - ngspice (
ngspice) — small-signal / transient (limited native RF) - scikit-rf (Python
skrf) — S-parameter math, stability (K/Δ), de-embedding - openEMS (
openEMS) — passive co-reference / S-param cross-check
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 · 308 lines · 134 tokens per session scan A 4c3e8797b7b5
rf-design is a skill published in the GitHub repository hdl-tools/analog-chip-design-agents (22 stars, last pushed 3mo ago), licensed MIT. It adds 134 tokens to every session and 3,644 once invoked, about $0.0007 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
neuroskill-bci
Use live BCI cognitive and mood state from NeuroSkill.
ruview-advanced-sensing
Advanced RuView capabilities — RuvSense multistatic sensing (attention-weighted fusion, geometric diversity, persistent field model), cross-viewpoint fusion across multiple nodes, RF tomography (ISTA L1 solver, voxel grids), longitudinal biomechanics drift, pre-movement intention signals, adversarial signal detection…
ruview-applications
Run RuView sensing applications — presence/occupancy, breathing & heart rate, activity & fall detection, 17-keypoint pose estimation (WiFlow), sleep monitoring & apnea screening, environment mapping, Mass Casualty Assessment (MAT), and the 3D point-cloud fusion demo. Use when someone wants to actually do something…
lab-hardware-cad
Design custom laboratory hardware as parametric build123d models and export fabrication-ready STEP, STL, and DXF files - microfluidic chips and molds, optomechanical mounts and breadboard adapters, cuvette and microplate holders, tube racks, animal-behavior rigs, and 3D-printed instrument fixtures. Use when a research…
opentrons-integration
Author, review, migrate, simulate, and troubleshoot official Opentrons Python Protocol API v2 protocols for Flex and OT-2 robots. Use for robot-specific liquid handling, deck and labware setup, pipettes, modules, runtime parameters, liquid classes, and Opentrons App analysis. Use pylabrobot instead when one workflow…
pylabrobot
Develop and review PyLabRobot lab-automation resources, liquid-handling plans, offline simulations, and supported-device integrations. Use for PyLabRobot protocols or API questions; keep physical execution behind an explicit operator safety gate.