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/review-circuit-simulationnpx skills add simra-tech/OpenADA --skill review-circuit-simulationgit clone --depth 1 https://github.com/simra-tech/OpenADAWrote 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/simra-tech/openada/review-circuit-simulation)<a href="https://agentmods.dev/skills/simra-tech/openada/review-circuit-simulation"><img src="https://agentmods.dev/badge/skills/simra-tech/openada/review-circuit-simulation.svg" alt="Measured on agentmods" 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 | $0.00091 | $0.01325 |
| Opus 5 | $0.00046 | $0.00662 |
| Sonnet 5 | $0.00018 | $0.00265 |
| Haiku 4.5 | $0.00009 | $0.00133 |
Grade B, and why
review-circuit-simulation scanned grade B with 1 finding 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 4d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
native `.measure` directives, print directives, control blocks, or additional How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Circuit Simulation
Use OpenADA's shared circuit-simulation operation as the execution boundary. Reason about the engineering question above that boundary, without teaching the workflow a simulator-specific CLI or log grammar.
Frame the decision
State the exact question before running anything. Keep these claims separate:
- Execution: Did the selected simulator run to completion?
- Evidence validity: Did the run produce fresh, structurally valid, finite evidence for the requested analysis under the shared operation profile?
- Series extraction: Were exact native vectors bound to a canonical real
series through
openada.operation/result.series.extract/v1alpha1? - Derived simulation result: What supported scalar can be derived from that series?
- Specification: Does that derived result meet an explicit limit?
The simulation profile can establish the first two claims. Compose the separate typed extraction, scalar-result, and specification operations only when their exact profiles are available. Require explicit selectors, scalar-result definitions, limits, units, corners, and model context before judging a design specification. Never upgrade valid simulation evidence into “the circuit works.”
Check applicability
openada.operation/circuit.simulate/v1alpha2 is the only simulation operation
and covers every form the request can arrive in: a bare deck or a published
Simra artifact, a model-free deck or one bound to an installed PDK by name, one
declared analysis or several. Require
openada.feature/simulation.analysis.<type>/v1alpha1 from the selected driver;
Xyce does not advertise OP.
A model-free deck must still be self-contained: one top-level OP, DC, AC, or
transient analysis with parseable closed parameters and no includes,
native .measure directives, print directives, control blocks, or additional
analyses. Model collateral is supplied as configuration - --pdk for an
installed PDK, --models for a flattened card file - and never pasted into the
deck. Never fall back to a raw native command while claiming comparable OpenADA
evidence.
What ships with it
1 file 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.
- 4d ago First seen · 130 lines · 91 tokens per session scan B 229d6f8f8ab9
review-circuit-simulation is a skill published in the GitHub repository simra-tech/OpenADA (24 stars, last pushed 22d ago), licensed MIT. It adds 91 tokens to every session and 1,325 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
timesfm-forecasting
Zero-shot time series forecasting with Google's TimesFM foundation model. Use this skill when forecasting ANY univariate time series — sales, sensor readings, stock prices, energy demand, patient vitals, weather, or scientific measurements — without training a custom model. Supports both basic forecasting and advanced…
parsing-hl7v2-messages
Decodes pipe-delimited HL7 v2.x messages (ADT, ORU, MDM, ORM) into structured segments/fields/components and surfaces OBX-5 and NTE-3 free-text narrative for OpenMed. Use before OpenMed processing when ingesting HL7 v2 feeds from an interface engine, lab/results system, or ADT stream and you need the embedded clinical…
spice
Run automatic SPICE simulations on subcircuits detected from KiCad schematic analysis — validates filter frequencies, divider ratios, opamp gains, LC resonance, and crystal load capacitance. Supports ngspice, LTspice, and Xyce (auto-detected). Generates testbenches, runs batch mode, produces structured pass/warn/fail…
omnisim-world-builder
Build, inspect, run, and debug OmniSim robotics worlds through the first-party MCP tools. Use for requests involving OmniSim scenes, robots, cameras, contacts, physics checks, or screenshots; do not use for unrelated simulators.
agopengps-knowledge-patch
Use this skill when designing, extending, deploying, or diagnosing AgOpenGPS, AgIO, AgValoniaGPS, AgOpenWeb, GNSS correction paths, autosteer hardware, or machine-control hardware. Start by identifying the exact application release, codebase, board revision, firmware source commit, and operating mode.
israeli-agritech-advisor
Guide developers in integrating Israeli agritech tools and precision agriculture platforms including CropX (soil monitoring), Netafim GrowSphere (IoT irrigation), Taranis (crop intelligence), and the broader Israeli agritech ecosystem. Use when user asks about agritech APIs, precision agriculture, smart irrigation…