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 LerianStudio/ring --skill reviewing-operational-riskgit clone --depth 1 https://github.com/LerianStudio/ringWrote 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/lerianstudio/ring/reviewing-operational-risk)<a href="https://agentmods.dev/skills/lerianstudio/ring/reviewing-operational-risk"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/reviewing-operational-risk/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/lerianstudio/ring/reviewing-operational-risk"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/reviewing-operational-risk.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.00123 | $0.03805 |
| Opus 5 | $0.00062 | $0.01903 |
| Sonnet 5 | $0.00025 | $0.00761 |
| Haiku 4.5 | $0.00012 | $0.00380 |
Grade A, and why
ring:reviewing-operational-risk 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 7d 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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operational Risk Review
When to use
- Preparing a service for production and want to know what breaks when a flow gets stuck
- After a dev-cycle: pressure-test the newly built flows for recovery gaps
- Incident retro: formalize which failure modes have a rescue path and which do not
- You need operational runbooks or a backlog of "missing rescue mechanism" gap specs
Skip when
- Prototype / throwaway PoC not heading to production
- Pure library or SDK with no integration boundaries (no external calls, queues, or webhooks)
- Single-question check (use a targeted read instead of the full review)
Related
Complementary: ring:auditing-production-readiness (broad readiness scoring), ring:mapping-service-resources (resource inventory), ring:running-dev-cycle (optional end-of-cycle hook)
What this produces
For every failure scenario, a tier and an actionable artifact:
| Tier | Meaning | Output |
|---|---|---|
| Tier 1 | The app resolves it itself — automatic retry, compensation, TTL/expiry, DLQ replay | Note only (documented as self-healing) |
| Tier 2 | An external trigger exists that unblocks it — an API call, an endpoint, a Console/UI action | Operational runbook with concrete steps |
| Tier 3 | Gap — no rescue path exists short of direct DB intervention | Gap spec (what's missing, who can act today, what should exist) |
Audience
The output is always written for the developer running the skill (tech lead or engineer). Runbooks assume operator access; gap specs assume backlog ownership.
How this skill runs: a hybrid (mechanical + judgement) flow
The review is split into two phases so the deterministic work is not left to the LLM:
Phase 1 — mechanical (scan-integration-points.mjs, run by the dev):
A zero-dependency Node.js script traverses the target repo and finds integration
boundaries (external HTTP calls, queue consumers, event publishers, outbound
webhooks). For each point it heuristically records whether retry, DLQ, timeout,
rollback/compensation, and idempotency patterns appear nearby. It emits a
structured JSON report. It is generic: it runs on any Go or TypeScript/Node.js
Lerian repo. This phase is repeatable and produces the same map every time.
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.
- 7d ago First seen · 286 lines · 123 tokens per session scan A 6c1dc51cd132
ring:reviewing-operational-risk is a skill published in the GitHub repository LerianStudio/ring (211 stars, last pushed 21d ago), licensed Apache-2.0. It adds 123 tokens to every session and 3,805 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
calibration
Internal dynos-work skill. Agent calibration — generates project-specific agents, benchmarks them, promotes/demotes based on performance, and manages auditor mode transitions. Runs only when the user explicitly types /dynos-work:calibration; never auto-triggered from conversation.
maintain
Internal dynos-work skill. Autonomous maintenance worker. Scans the repo for technical debt, security anti-patterns, and architectural drift; on a finding it creates a repair branch, implements the fix, verifies with audits/tests, and opens a Pull Request. Runs only when the user explicitly types /dynos-work:maintain…
ds-brief
Data-backed brief — research, source, double-verify, and render a visually rich single-file HTML report. Use when the user wants a sourced, fact-checked brief or report on a topic.
ds-ship
Ship orchestrator — classify the project, pick a mode (improve/release/launch/maintain), delegate only the skills the project's signals justify, consolidate findings, produce an audit report. Use for an end-to-end audit or ship pipeline across multiple skills.
ds-test
Universal test skill — generate, update, run, and fix tests for any stack. Use when writing, repairing, or running tests, or improving coverage.
local
Internal dynos-work skill. Manage the project daemon: start, stop, status, logs, run-once, dashboard. Runs only when the user explicitly types /dynos-work:local; never auto-triggered from conversation.