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/characterize-analog-blocknpx skills add simra-tech/OpenADA --skill characterize-analog-blockgit 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/characterize-analog-block)<a href="https://agentmods.dev/skills/simra-tech/openada/characterize-analog-block"><img src="https://agentmods.dev/badge/skills/simra-tech/openada/characterize-analog-block.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.00094 | $0.03162 |
| Opus 5 | $0.00047 | $0.01581 |
| Sonnet 5 | $0.00019 | $0.00632 |
| Haiku 4.5 | $0.00009 | $0.00316 |
Grade A, and why
characterize-analog-block 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 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.
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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Characterize an Analog Block
Act as the characterization coordinator. Turn the application and specifications
into the smallest justified sequence of OpenADA intents, then delegate focused
reviews to the other engineering skills. Use $openada:openada for capability discovery,
invocation, and result interpretation. Keep native design data, testbenches, PDKs,
models, and artifacts authoritative.
Preserve the contract ladder
Keep these conclusions separate at every step:
| Layer | Exact semantic boundary | Strongest allowed conclusion |
|---|---|---|
| Analysis evidence | openada.operation/circuit.simulate/v1alpha2 with openada.assertion/simulation.evidence.valid/v1alpha1 |
The requested OP, DC, AC, or transient analysis produced valid evidence, or conclusively did not converge |
| Series extraction | openada.operation/result.series.extract/v1alpha1 with openada.assertion/series.extraction.valid/v1alpha1 |
Exact native vectors were bound to a canonical real series with verified artifact lineage |
| Scalar simulation result | openada.operation/result.measure/v1alpha2 with openada.assertion/measurement.valid/v1alpha1 |
The declared metric was validly extracted from identified source evidence |
| Spectral simulation result | openada.operation/result.spectral.measure/v1alpha1 with openada.assertion/spectral.measurement.valid/v1alpha1 |
One declared coherent SNR, SINAD, THD, or SFDR ratio was validly derived |
| AC transfer simulation result | openada.operation/result.transfer.measure/v1alpha2 with openada.assertion/transfer.measurement.valid/v1alpha1 |
One declared gain, driving-point impedance, bandwidth, unity-frequency, or negative-feedback phase-margin scalar was validly derived, over single-ended or differential operands |
| Oscillator simulation result | Experimental openada.operation/result.osc.measure/v1alpha1 with openada.assertion/oscillator.measurement.valid/v1alpha1 |
One declared same-window oscillator transient has a typed sustained/non-result verdict, or complete transient receipts were validly composed into local Kvco, span, or perturbation shift |
| Specification | openada.operation/specification.evaluate/v1alpha1 with openada.assertion/specification.satisfied/v1alpha1 |
The declared simulation result satisfies or violates the explicit limit under its recorded conditions |
| Signoff | Outside these assertions | Only a separately qualified flow and accountable reviewer may make a signoff claim |
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.
- 4d ago First seen · 265 lines · 94 tokens per session scan A 72f9f486b93d
characterize-analog-block is a skill published in the GitHub repository simra-tech/OpenADA (24 stars, last pushed 22d ago), licensed MIT. It adds 94 tokens to every session and 3,162 once invoked, about $0.0005 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
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.
aria-knowledge
Encoded knowledge for Project Aria Gen 2 and the Aria Research Kit (ARK) — hardware, profiles, calibration, coordinate systems, VRS format, time domains, on-device perception, MPS outputs (SLAM, point cloud, hand tracking), plus pointers to the source-of-truth docs for specifics. Use whenever the user asks ANY…