What is infraops-escalation?

Instructions for extending the InfraOps MCP server when it lacks an infrastructure operation, provider, parameter, or tool. InfraOps is an integration for working with infrastructure services.

Escalating unsupported infrastructure operations to the InfraOps provider agent, while leaving deployments, restarts, and destructive changes to Devon.

It provides a defined way to request missing server capabilities instead of abandoning the task or treating routine tool use as an extension request.

infraops-escalation — Skill for Claude Code and Codex by AlobarQuest

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 AlobarQuest/infraops-mcp-server --skill skill

Clone the repo

git clone --depth 1 https://github.com/AlobarQuest/infraops-mcp-server

Made for: Claude Code, 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/alobarquest/infraops-mcp-server/skill/github.svg)](https://agentmods.dev/skills/alobarquest/infraops-mcp-server/skill)

Your own site

<a href="https://agentmods.dev/skills/alobarquest/infraops-mcp-server/skill"><img src="https://agentmods.dev/badge/skills/alobarquest/infraops-mcp-server/skill/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/alobarquest/infraops-mcp-server/skill"><img src="https://agentmods.dev/badge/skills/alobarquest/infraops-mcp-server/skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 162 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 812 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.

Model	Per session	Once invoked
Fable 5.1	$0.00162	$0.00812
Opus 5.5	$0.00065	$0.00325
Sonnet 5.5	$0.00032	$0.00162
Haiku 4.5	$0.00016	$0.00081

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

Security

Grade A, and why

infraops-escalation 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 2mo 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.

skill/SKILL.md · 61 lines

How it starts

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

Escalate to the InfraOps provider agent

The infraops MCP exposes ~195 infrastructure tools. When you need something it doesn't expose — no tool for an operation, a tool missing a parameter, an unsupported provider endpoint — you don't have to give up or hand it to Devon. You can escalate to the infraops provider agent: a gated agent running inside ~/Projects/infraops-mcp-server that can reason about the server and add or extend a tool to close the gap.

This is an escalation lane, not basic usage. If the MCP already has a tool for what you need, just call it.

When to escalate

The capability you need has no infraops tool at all.
An existing tool is close but missing a parameter / option you need.
A provider endpoint isn't covered and adding it is in scope for infraops.

When NOT to escalate

Routine work an existing tool covers → just call the tool.
The fix is an infrastructure mutation (deploy, restart, destructive op) → that's Devon's call; the provider agent will refuse it and emit it as a PROPOSAL anyway.

How to escalate

~/Projects/infraops-mcp-server/bin/provider-agent --session <short-issue-name> \
  "Doing <infra task> for <app>. I need <capability> but the infraops MCP has no
   tool for it / tool <name> lacks <param>. Here's what I tried and the exact error: …"

Give it full context: the operation you need, the closest existing tool (if any), what you tried, and exact errors. Reuse one --session name per issue so the thread keeps context across turns.

Read the `STATUS:` block in the reply

resolved — the provider agent added/extended the tool. Its edits are on a provider-agent/<session> review branch in ~/Projects/infraops-mcp-server (the reply's [provider-agent] … committed to <branch> @ <sha> line names it). The new tool is not live yet: Devon reviews/merges the branch, then the MCP is rebuilt (npm run build) and reloaded before the tool can be called. Surface this to Devon; don't assume the tool is immediately callable.
needs-info — it needs more from you. Answer precisely and call again with the same --session name.
needs-devon — closing the gap needs an infra mutation or a build/publish only Devon should authorize. Stop and surface the PROPOSALS block to Devon.

Read the full file on GitHub · 61 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.

2mo ago First seen · 61 lines · 162 tokens per session scan A 6137178d287f

Subscribe to this mod's changes

infraops-escalation is a skill published in the GitHub repository AlobarQuest/infraops-mcp-server (0 stars, last pushed yesterday), licensed MIT. It adds 162 tokens to every session and 812 once invoked, about $0.0006 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-31.

DevOps and cloud

infraops-escalation next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
infraops-escalationAlobarQuest/infraops-mcp-server	Skill	0	yesterday	MIT	A	162	Claude Code, Codex
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	yesterday	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	100k	yesterday	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	4d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code