Borrowing it
Nothing to install: this file belongs to secure-ssid/hpe-networking-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.
curl -O https://raw.githubusercontent.com/secure-ssid/hpe-networking-mcp/main/.github/skills/operator-runbooks/SKILL.mdgit clone --depth 1 https://github.com/secure-ssid/hpe-networking-mcpWrote 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/secure-ssid/hpe-networking-mcp/operator-runbooks)<a href="https://agentmods.dev/skills/secure-ssid/hpe-networking-mcp/operator-runbooks"><img src="https://agentmods.dev/badge/skills/secure-ssid/hpe-networking-mcp/operator-runbooks/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/secure-ssid/hpe-networking-mcp/operator-runbooks"><img src="https://agentmods.dev/badge/skills/secure-ssid/hpe-networking-mcp/operator-runbooks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00087 | $0.00447 |
| Opus 5 | $0.00044 | $0.00224 |
| Sonnet 5 | $0.00017 | $0.00089 |
| Haiku 4.5 | $0.00009 | $0.00045 |
Grade A, and why
operator-runbooks 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.
What it actually says
operator-runbooks skill
Bundled runbooks live on rag-core and are reached through the router.
Browse
invoke_read_tool("list_skills", {"detail": false})
invoke_read_tool("list_skills", {"platform": "central", "tag": "audit"})
invoke_read_tool("list_skills", {"platform": "mist"})
list_skills returns metadata only. Always load_skill before executing.
Load
invoke_read_tool("load_skill", {"name": "morning-report"})
invoke_read_tool("load_skill", {"name": "central-scope-walker"})
invoke_read_tool("load_skill", {"name": "central-scope-audit"})
invoke_read_tool("load_skill", {"name": "wlan-sync-validation"})
invoke_read_tool("load_skill", {"name": "cross-platform-rf-check"})
invoke_read_tool("load_skill", {"name": "clearpass-policy-audit"})
invoke_read_tool("load_skill", {"name": "mist-scope-audit"})
invoke_read_tool("load_skill", {"name": "uxi-diagnostics"})
invoke_read_tool("load_skill", {"name": "aos8-migration-readiness"})
Execution rules
- Router pattern:
find_tool→invoke_read_tool(reads) /invoke_tool(writes). - Honor each runbook's read-only vs gated-write sections.
- If a product backend is missing, say so — do not hallucinate tool results.
- Optional products need
HPE_MCP_PRODUCTS(clearpass, mist, aos8, uxi, …).
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.
- 10d ago First seen · 45 lines · 87 tokens per session scan A 855d21b2c4f8
operator-runbooks is a skill published in the GitHub repository secure-ssid/hpe-networking-mcp (1 stars, last pushed 6d ago), licensed MIT. It adds 87 tokens to every session and 447 once invoked, about $0.0004 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.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, offers to turn Diagnostics on when the project has it…
ue-mcp-epic-routing
Use when deciding between ue-mcp's native category actions and Epic's wrapped ToolsetRegistry tools (the epic actions, incl. the Blueprint graph DSL) for a task in Unreal. Pulls in when authoring Blueprint graph bodies, or any time both a native action and an epic action could do the job and you need to pick.
mcp-google-map-project
Project knowledge for developing and maintaining @cablate/mcp-google-map. Architecture, Google Maps API guide, GIS domain knowledge, and design decisions. Read this skill to onboard onto the project or make informed development decisions.
frontmcp-setup
Use when starting, scaffolding, or organizing a FrontMCP project. Covers creating a new project (CLI scaffold or manual) for Node, Vercel, and other targets; standalone versus Nx-monorepo layout, naming conventions, generators, and dependency rules; composing multiple @App classes, ESM packages, and remote MCP servers…