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-feedback-stabilitynpx skills add simra-tech/OpenADA --skill analyze-feedback-stabilitygit clone --depth 1 https://github.com/simra-tech/OpenADAWhat 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.00078 | $0.01720 |
| Opus 5 | $0.00039 | $0.00860 |
| Sonnet 5 | $0.00016 | $0.00344 |
| Haiku 4.5 | $0.00008 | $0.00172 |
Grade A, and why
analyze-feedback-stability 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 3d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Feedback Stability
Produce an evidence-bounded diagnosis, not a universal compensation recipe.
Use $openada:openada to invoke semantic operations and interpret results. Keep the
topology, prepared testbench, PDK/models, and native artifacts authoritative.
Separate the claims
Use these exact layers:
- Establish analysis evidence with
openada.operation/circuit.simulate/v1alpha2andopenada.assertion/simulation.evidence.valid/v1alpha1. - Bind the exact native AC Cartesian vectors through
openada.operation/result.series.extract/v1alpha1andopenada.assertion/series.extraction.valid/v1alpha1. - Derive the implemented loop metrics only through
openada.operation/result.transfer.measure/v1alpha2andopenada.assertion/transfer.measurement.valid/v1alpha1. - Derive ordinary time-domain or real-series scalars only through
openada.operation/result.measure/v1alpha2andopenada.assertion/measurement.valid/v1alpha1. - Judge an explicit stability limit only through
openada.operation/specification.evaluate/v1alpha1andopenada.assertion/specification.satisfied/v1alpha1.
Inspect capability records, then run openada profile show openada.operation/result.transfer.measure/v1alpha2 before constructing a
request. Do not invent a metric kind or fall back to a backend expression when
the requested result.transfer.measure metric kind is not supported. Mark that
metric not evaluated.
None of these layers alone establishes silicon, reliability, or signoff.
Freeze one baseline
Record:
- authoritative design/testbench identity and design phase;
- supply, bias, common mode, differential stimulus, load, corner, temperature, and operating mode;
- enabled paths, stages, switches, feedback elements, and intended loop state;
- exact loop break or injection point, direction/sign convention, return probe, loop-response signals, and requested closed-loop probes;
- selected operation/feature, driver, native product/version, request/result IDs, and evidence destination.
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.
- 3d ago First seen · 167 lines · 78 tokens per session scan A 85eb1553f1ad
analyze-feedback-stability is a skill published in the GitHub repository simra-tech/OpenADA (24 stars, last pushed 21d ago), licensed MIT. It adds 78 tokens to every session and 1,720 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
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…
extracting-pii-entities
Detect PHI/PII spans in clinical text with OpenMed's extractpii without altering the text. Use when the user wants to find names, dates, MRNs, phone numbers, addresses, SSNs, or other identifiers and get their offsets and labels (not redact them), inspect what would be removed before de-identifying, route spans to a…
overleaf-sync
Two-way sync between a local paper directory and an Overleaf project, so ARIS audit/edit workflows stay on the local copy while collaborators edit in the Overleaf web UI. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to…
mixed-precision
Use FP16/BF16 mixed precision to accelerate training and reduce memory. Use when optimizing GPU performance.
tooluniverse-electron-microscopy
Search and analyze electron microscopy data — cryo-EM density maps (EMDB), fitted atomic models (PDB), raw micrograph datasets (EMPIAR), and cryo-electron tomography volumes (CryoET Data Portal). Use for finding 3D structural data on a protein/complex, comparing experimental EM resolution to AlphaFold confidence, and…