openrouter-mcp: Skill for Codex

.agents/skills/mcp-config-ops/SKILL.md

mcp-config-ops is a skill for Codex from physics91/openrouter-mcp. It costs 36 tokens per session (544 once invoked), scanned A, original, MIT.

A maintenance workflow for installing or repairing MCP settings in Claude Desktop or Claude Code. MCP settings tell these clients which external tool servers to start.

In plain words
What is it for?
Use it to inspect MCP configuration, back up files, install or repair the Claude clients' settings, and verify the result.
Why use it?
It reduces configuration drift and protects existing settings by checking status and creating backups before changes.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions Claude Code; 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 →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node bin/openrouter-mcp.js status.

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/mcp-config-ops/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 mcp-config-ops

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/physics91/openrouter-mcp/mcp-config-ops"><img src="https://agentmods.dev/badge/skills/physics91/openrouter-mcp/mcp-config-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 544 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.00036 $0.00544
Opus 5 $0.00018 $0.00272
Sonnet 5 $0.00007 $0.00109
Haiku 4.5 $0.00004 $0.00054

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

Security

Grade A, and why

mcp-config-ops 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 9d 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/mcp-config-ops/SKILL.md · 73 lines

How it starts

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

Mcp Config Ops

Overview

Use this skill when a task touches MCP client configuration rather than core model behavior. It standardizes status checks, backup discipline, installer flows, and config-drift troubleshooting for the repository's Node-to-Python bootstrap path.

Repository Touchpoints

  • bin/openrouter-mcp.js
  • src/openrouter_mcp/cli/mcp_manager.py
  • src/openrouter_mcp/cli/commands.py
  • src/openrouter_mcp/server.py
  • docs/CLAUDE_DESKTOP_GUIDE.md
  • docs/CLAUDE_CODE_GUIDE.md
  • docs/INSTALLATION.md

Standard Workflow

  1. Inspect the current state:
    node bin/openrouter-mcp.js status
    
  2. Identify the target client:
    • Claude Desktop
    • Claude Code
    • both
  3. Back up any config file before mutation.
  4. Apply one installer or repair action at a time:
    node bin/openrouter-mcp.js install-claude
    node bin/openrouter-mcp.js install-claude-code
    
  5. Re-run status and inspect the written config path.
  6. If documentation changed, verify that package names and command examples still match the actual CLI path.

Backup And Restore Rules

  • Never overwrite a user config file without first capturing a backup path.
  • If the installer already creates backups, record where they are.
  • If an install or migration goes wrong, restore the backup before trying a second fix path.

Consistency Checks

  • Check command examples against the actual package scope:
    rg -n "@physics91/openrouter-mcp|openrouter-mcp" README.md docs
    
  • Watch for drift between install docs and actual CLI behavior.
  • Treat Node/Python bootstrap issues as part of config operations when they block installation or status checks.

Recovery Pattern

If config drift or install failure is reported:

  1. Capture the failing path and command.
  2. Compare generated config with the documented expected shape.
  3. Restore backup if the generated output is clearly wrong.
  4. Re-run a single installer path.
  5. Finish by running status again.

Done Definition

Read the full file on GitHub · 73 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. 9d ago First seen · 73 lines · 36 tokens per session scan A 0b3cd6fd5fe3

Subscribe to this mod's changes

mcp-config-ops is a skill published in the GitHub repository physics91/openrouter-mcp (9 stars, last pushed 27d ago), licensed MIT. It adds 36 tokens to every session and 544 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