openrouter-mcp: Skill for Codex

.agents/skills/resilience-policy/SKILL.md

resilience-policy is a skill for Codex from physics91/openrouter-mcp. It costs 31 tokens per session (567 once invoked), scanned A, original, MIT.

A set of rules for changing reliability controls in a collective-intelligence system, such as limits on simultaneous work, usage quotas, circuit breakers, and cleanup.

In plain words
What is it for?
Use it when changing concurrency limits, quota handling, failure recovery, circuit-breaker behavior, or shutdown and cleanup code.
Why use it?
It keeps high-risk operational changes from leaking resources, losing bounded memory, mishandling failures, or skipping cleanup after errors and cancellation.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

This is physics91/openrouter-mcp's own configuration. It tells Codex how to work on openrouter-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything openrouter-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to physics91/openrouter-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/physics91/openrouter-mcp/main/.agents/skills/resilience-policy/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/physics91/openrouter-mcp

Made for: Codex.

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 resilience-policy

README.md
[![agentmods](https://agentmods.dev/badge/skills/physics91/openrouter-mcp/resilience-policy/github.svg)](https://agentmods.dev/skills/physics91/openrouter-mcp/resilience-policy)
Your own site
<a href="https://agentmods.dev/skills/physics91/openrouter-mcp/resilience-policy"><img src="https://agentmods.dev/badge/skills/physics91/openrouter-mcp/resilience-policy/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 resilience-policy

Your own site · 80×15
<a href="https://agentmods.dev/skills/physics91/openrouter-mcp/resilience-policy"><img src="https://agentmods.dev/badge/skills/physics91/openrouter-mcp/resilience-policy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 567 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.00031 $0.00567
Opus 5 $0.00015 $0.00283
Sonnet 5 $0.00006 $0.00113
Haiku 4.5 $0.00003 $0.00057

Measured 10d ago against content hash 7965ac1ffc90, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

resilience-policy 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 10d 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.

.agents/skills/resilience-policy/SKILL.md · 72 lines

How it starts

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

Resilience Policy

Overview

Use this skill for changes where correctness depends on operational invariants rather than one user-facing feature. It keeps concurrency, quota, circuit-breaker, and cleanup edits tied to explicit invariants and targeted verification.

Primary Files In Scope

  • src/openrouter_mcp/collective_intelligence/operational_controls.py
  • src/openrouter_mcp/collective_intelligence/consensus_engine.py
  • src/openrouter_mcp/collective_intelligence/collaborative_solver.py
  • src/openrouter_mcp/collective_intelligence/lifecycle_manager.py
  • src/openrouter_mcp/handlers/mcp_benchmark.py
  • tests/test_operational_controls.py
  • tests/test_lifecycle_manager.py
  • tests/test_collective_intelligence/

Required Invariants

  • Every acquired slot, semaphore, or limiter path must release symmetrically.
  • In-memory history and buffers must stay bounded.
  • Failure counters and circuit state must have explicit reset or recovery semantics.
  • Cleanup and shutdown paths must still run when execution errors or cancellations happen.
  • Degraded behavior must be explicit; do not silently swallow policy failures.

Change Workflow

  1. Name the invariant being changed before editing code.
  2. Add or adjust the failing test first.
  3. Keep the implementation minimal and policy-focused.
  4. Run the narrowest targeted tests that prove the invariant.
  5. If the change touches shared execution behavior, widen verification to assurance or the most relevant integration slice.

Verification Targets

Start with targeted tests such as:

python3 -m pytest tests/test_operational_controls.py -v
python3 -m pytest tests/test_lifecycle_manager.py -v
python3 -m pytest tests/test_collective_intelligence/ -v

Escalate when needed:

python3 run_tests.py integration -v
python3 run_tests.py assurance -v

If the policy change affects replay, property, or performance behavior, run the relevant suite instead of assuming the narrower tests are enough.

Red Flags

Read the full file on GitHub · 72 lines

Files

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.

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. 10d ago First seen · 72 lines · 31 tokens per session scan A 7965ac1ffc90

Subscribe to this mod's changes

resilience-policy is a skill published in the GitHub repository physics91/openrouter-mcp (9 stars, last pushed 27d ago), licensed MIT. It adds 31 tokens to every session and 567 once invoked, about $0.0002 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens