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.
npx agentmods add skills/runwhen-contrib/runwhen-platform-mcp/build-operational-contextnpx skills add runwhen-contrib/runwhen-platform-mcp --skill build-operational-contextgit clone --depth 1 https://github.com/runwhen-contrib/runwhen-platform-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/runwhen-contrib/runwhen-platform-mcp/build-operational-context)<a href="https://agentmods.dev/skills/runwhen-contrib/runwhen-platform-mcp/build-operational-context"><img src="https://agentmods.dev/badge/skills/runwhen-contrib/runwhen-platform-mcp/build-operational-context.svg" alt="Measured on agentmods" 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.00095 | $0.01345 |
| Opus 5 | $0.00048 | $0.00673 |
| Sonnet 5 | $0.00019 | $0.00269 |
| Haiku 4.5 | $0.00010 | $0.00135 |
Grade A, and why
build-operational-context 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Operational Context
Guide for progressing through the RunWhen operational context maturity model. Reference: https://docs.runwhen.com/guides/building-operational-context/
Maturity levels
| Level | What to add | Tools | Skill |
|---|---|---|---|
| 1 — Foundation | Tasks against live infrastructure | commit_slx, run_slx |
build-runwhen-task, run-existing-slx |
| 2 — Signal | Rules for noise suppression + priority framing | create_chat_rule, update_chat_rule |
manage-rules |
| 3 — Standardization | Commands for repeatable procedures + Knowledge for institutional context | create_chat_command, create_knowledge_base_article |
manage-commands, manage-knowledge |
| 4 — Integration | Automated context from CI/CD, incidents, change management | All API tools | (engineering integration) |
Quick workflow
Step 1: Capture a baseline
Run a prompt your team asks often through workspace_chat:
workspace_chat(workspace_name="my-workspace", message="What's unhealthy in my-namespace?")
Note the quality: Is it focused? Are expected issues over-emphasized? Are next steps specific? This is your Level 1 baseline.
Step 2: Add Rules (→ Level 2)
See the manage-rules skill for detailed guidance.
Start with 2-3 rules addressing the biggest noise sources:
create_chat_rule(
name="Deprioritize Node Pressure",
rule_content="Node pressure in shared lab clusters is expected. Mention briefly but prioritize app-level issues first.",
scope_type="workspace",
scope_id="my-workspace"
)
Re-run your baseline prompt. Compare focus, clarity, and actionability.
Step 3: Add Commands (→ Level 3)
See the manage-commands skill for detailed guidance.
Create 1-2 commands for your most common investigation patterns:
create_chat_command(
name="investigate-namespace",
command_content="Investigate pod status, events, error logs, resource pressure, and dependencies. Group findings by severity with specific next steps.",
scope_type="workspace",
scope_id="my-workspace"
)
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.
- 6d ago First seen · 134 lines · 95 tokens per session scan A 28b18fc3362e
build-operational-context is a skill published in the GitHub repository runwhen-contrib/runwhen-platform-mcp (1 stars, last pushed 22d ago), licensed Apache-2.0. It adds 95 tokens to every session and 1,345 once invoked, about $0.0005 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
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.
n8n-self-hosting
Deploy a production self-hosted n8n end-to-end to a fresh Linux VM over SSH, using Docker Compose behind a Caddy reverse proxy with automatic HTTPS. Use whenever the user wants to self-host, install, set up, provision, or deploy n8n on their own server/VPS/box (Hetzner, DigitalOcean, AWS EC2, bare metal, etc.) — in…
cloud-run
Manage Cloud Run services and jobs.
modal
Use when the user needs to run isolated code remotely — a disposable container, optional GPU access (T4 → H100), or a safer place for untrusted / heavy code. Prefer local execution for normal repo work; use Modal sandboxes for isolation, hardware access, or one-shot heavy compute.
cluster-events
Analyze cluster-wide Kubernetes events to identify issues and patterns. Aggregates Warning events, detects high-frequency patterns, and correlates related events.
k8s-pod-rightsizer
Analyze Kubernetes workload metrics and produce policy-constrained CPU/memory rightsizing recommendations with optional patch generation and rollback-safe apply.