design-operational-risk-framework

design-operational-risk-framework is a skill for Claude Code from jeffreytse/grimoire-core. It costs 73 tokens per session (1,521 once invoked), scanned A, original, MIT.

A structured way to manage losses caused by failed processes, people, systems, or outside events. It organizes risks into types, tracks warning signs, and checks whether controls are working.

In plain words
What is it for?
Use it to define loss categories, create key risk indicators, assess controls, assign owners, and review operational risks regularly.
Why use it?
It replaces a vague view of operational risk with a repeatable method for finding, monitoring, and reducing specific weaknesses.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the grimoire-business plugin — 156 skills shipped together

Good fit Use it to define loss categories, create key risk indicators, assess controls, assign owners, and review operational risks regularly.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffreytse/grimoire-core/design-operational-risk-framework
Install

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.

Any agent
npx skills add jeffreytse/grimoire-core --skill design-operational-risk-framework
Clone the repo
git clone --depth 1 https://github.com/jeffreytse/grimoire-core

Made for: Claude Code.

Or install grimoire-business, the plugin that ships this one along with the rest of its 156 skills.

Wrote 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.

agentmods badge for design-operational-risk-framework

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-operational-risk-framework/github.svg)](https://agentmods.dev/skills/jeffreytse/grimoire-core/design-operational-risk-framework)
Your own site
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/design-operational-risk-framework"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-operational-risk-framework/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.

agentmods 80×15 button for design-operational-risk-framework

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/design-operational-risk-framework"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-operational-risk-framework.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,521 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00073 $0.01521
Opus 5.5 $0.00029 $0.00608
Sonnet 5.5 $0.00015 $0.00304
Haiku 4.5 $0.00007 $0.00152

Measured 1mo ago against content hash 7bd84da15fd0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

design-operational-risk-framework 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.

skills/business/operations/skills/design-operational-risk-framework/SKILL.md · 68 lines

How it starts

The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design Operational Risk Framework

Manage the risk of loss arising from failed internal processes, people, systems, or external events by organizing operational risk into a specific loss-event taxonomy, tracking key risk indicators that provide early warning of rising operational risk, and running periodic risk-control self-assessments — rather than treating "operational risk" as a vague catch-all category with no structured process of its own.

Why This Is Best Practice

Adopted by: The Basel Committee on Banking Supervision's "Sound Practices for the Management and Supervision of Operational Risk" establishes operational risk as a distinct risk category (alongside credit and market risk) requiring its own structured management framework, including a standard loss-event taxonomy (internal fraud, external fraud, employment practices, clients/products/business practices, damage to physical assets, business disruption and system failures, and execution/delivery/process management), and this structured approach has become standard practice across regulated financial institutions and increasingly across other large organizations managing operational risk. Impact: Organizations that treat operational risk as an undifferentiated catch-all — "anything that isn't market or credit risk" — tend to lack the specific tools (a defined loss-event taxonomy, tracked leading indicators, systematic control self-assessment) needed to actually identify, measure, and manage this risk category with the same rigor applied to market and credit risk, resulting in operational losses that a more structured framework would have provided earlier warning of or better prevented. Why best: Operational risk spans a genuinely diverse set of failure types — internal fraud, system outages, process errors, external events — that don't share a common driver the way market risk (price movements) or credit risk (counterparty default) do; a specific taxonomy and dedicated tracking tools (key risk indicators, risk-control self-assessments) are needed to bring the same structured rigor to this diverse category that other risk types already receive by default, rather than leaving it as an unstructured residual category.

Read the full file on GitHub · 68 lines

Changes

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.

  1. 1mo ago First seen · 68 lines · 73 tokens per session scan A 7bd84da15fd0

Subscribe to this mod's changes

design-operational-risk-framework is a skill published in the GitHub repository jeffreytse/grimoire-core (5 stars, last pushed 5d ago), licensed MIT. It adds 73 tokens to every session and 1,521 once invoked, about $0.0003 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-09-03.