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/analyze-spectral-linearitynpx skills add simra-tech/OpenADA --skill analyze-spectral-linearitygit 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/analyze-spectral-linearity)<a href="https://agentmods.dev/skills/simra-tech/openada/analyze-spectral-linearity"><img src="https://agentmods.dev/badge/skills/simra-tech/openada/analyze-spectral-linearity.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.00080 | $0.01767 |
| Opus 5 | $0.00040 | $0.00883 |
| Sonnet 5 | $0.00016 | $0.00353 |
| Haiku 4.5 | $0.00008 | $0.00177 |
Grade A, and why
analyze-spectral-linearity 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Spectral Linearity
Treat each spectral metric as a simulation result derived from identified
waveform evidence, not as a simulator side effect. Use $openada:openada for
semantic operations and normalized results; keep the exact testbench and native
waveform artifact authoritative.
Preserve the contract layers
- Establish waveform evidence with
openada.operation/circuit.simulate/v1alpha2andopenada.assertion/simulation.evidence.valid/v1alpha1. - Bind exact native vectors to a real sampled record with
openada.operation/result.series.extract/v1alpha1andopenada.assertion/series.extraction.valid/v1alpha1. - Extract an implemented coherent single-tone ratio with
openada.operation/result.spectral.measure/v1alpha1andopenada.assertion/spectral.measurement.valid/v1alpha1. - Use ordinary time-domain scalar algorithms through
openada.operation/result.measure/v1alpha2andopenada.assertion/measurement.valid/v1alpha1. - Evaluate declared limits with
openada.operation/specification.evaluate/v1alpha1andopenada.assertion/specification.satisfied/v1alpha1.
Inspect installed capability records and parameter schemas before forming a
request. Use openada profile show openada.operation/result.spectral.measure/v1alpha1 for the packaged closed
schema. The implemented spectral alpha covers SNR, SINAD, THD, and SFDR only
for its exact coherent rectangular method. A different window, noncoherent
record, sine fit, PSD, averaging, SNDR alias, ENOB, jitter, or phase-noise
question remains not evaluated — capability unavailable. Never present an
ad hoc script or backend expression as a result.spectral.measure result.
Read references/standards-and-methods.md when a metric is connected to an ADC, DAC, waveform recorder, pulse, jitter, or IEEE standard.
Freeze provenance and signal meaning
Record:
- exact testbench, configuration, corner, temperature, mode, stimulus, clock, driver, native product/version, and run/result identity;
- native waveform artifact identity and the requested transient interval;
- source signal names and whether the analyzed signal is differential, common-mode, single-ended, or a declared mathematical combination;
- fundamental or clock source and how its frequency was established;
- requested metric, units, included/excluded content, and specification source.
What ships with it
2 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 · 165 lines · 80 tokens per session scan A 7bb8276a378f
analyze-spectral-linearity is a skill published in the GitHub repository simra-tech/OpenADA (24 stars, last pushed 22d ago), licensed MIT. It adds 80 tokens to every session and 1,767 once invoked, about $0.0004 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
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…
auditing-subgroup-fairness
Audit an OpenMed NER or de-identification model for performance disparities across demographic subgroups (sex, age band, race/ethnicity when available) using openmed.eval.fairnessreport. Use when the user wants per-subgroup recall and leakage, wants to check whether de-identification under-protects a group, wants to…
mixed-precision
Use FP16/BF16 mixed precision to accelerate training and reduce memory. Use when optimizing GPU performance.
tooluniverse-drug-research
Comprehensive drug profiling — mechanism, primary/secondary targets, drug interactions, clinical-trial status, adverse events (FAERS), pharmacogenomics, and approval history. Use for full drug investigation reports, 'tell me about drug X' queries, and assembling drug profiles for clinicians, researchers, or regulatory…