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 ai-analyst-lab/ai-analyst-plugin --skill reliabilitygit clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst-pluginWrote 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/ai-analyst-lab/ai-analyst-plugin/reliability)<a href="https://agentmods.dev/skills/ai-analyst-lab/ai-analyst-plugin/reliability"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst-plugin/reliability/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/ai-analyst-lab/ai-analyst-plugin/reliability"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst-plugin/reliability.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00093 | $0.01320 |
| Opus 5.5 | $0.00037 | $0.00528 |
| Sonnet 5.5 | $0.00019 | $0.00264 |
| Haiku 4.5 | $0.00009 | $0.00132 |
Grade A, and why
reliability 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- reliability — 86% identical, 40 lines differ
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Reliability check
Purpose
Run one analytics question several independent times and report whether the answer is stable (every run agrees) or drifting (runs disagree because the question is under-defined). Stability is necessary, not sufficient: a wrong query is perfectly stable. This check needs no ground truth.
Invocation
/reliability "<the question>" [N] — default N = 5.
Example: /reliability "What's our retention rate?"
How to run it
Step 1 — fire N independent runs
Launch N sub-agents in parallel with the Task/Agent tool (N defaults to 5). They must be genuinely independent: each gets a fresh context and sees ONLY the question, never the other runs' answers. Give each sub-agent exactly this brief:
You are answering one analytics question against the active dataset. Load the normal session context first (knowledge-bootstrap: read
.knowledge/active.yaml, then the active dataset'sschema.md,quirks.md, and manifest from the local datasets dir). For the metric dictionary and semantic context, first resolve the context dir: read.knowledge/context-source.yaml; if it exists and sayssource: git, clone or pull the repo it names into.knowledge/.context-cache(checkout theref, defaultmain) and use the dataset's directory inside that cache; otherwise use.knowledge/datasets/{active}/. Readmetrics/index.yamlandsemantic/from the RESOLVED dir, not from any other copy. Do not read.knowledge/reliability/history before answering. If the metric you're asked about is defined in the dictionary, use that definition exactly. If it is not, decide for yourself how best to define and measure it. Query the real data through the session's active data connection (the mounted files or the connected warehouse). Answer the question: "". Then return ONLY this block:headline: <the single number you'd report>measured: <one line: numerator, denominator, grain, window, any filter>definition_source: <"metric dictionary" if you used a defined metric, else "my own choice">
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.
- 1mo ago First seen · 92 lines · 93 tokens per session scan A 3c022e449a1d
reliability is a skill published in the GitHub repository ai-analyst-lab/ai-analyst-plugin (33 stars, last pushed 1mo ago), licensed MIT. It adds 93 tokens to every session and 1,320 once invoked, about $0.0004 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…