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 instructions/runwhen-contrib/runwhen-platform-mcp/copilot-instructionsgit 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/instructions/runwhen-contrib/runwhen-platform-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/runwhen-contrib/runwhen-platform-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/runwhen-contrib/runwhen-platform-mcp/copilot-instructions.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 | $0.00562 | $0.00562 |
| Opus 5 | $0.00281 | $0.00281 |
| Sonnet 5 | $0.00112 | $0.00112 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
runwhen-platform-mcp copilot-instructions.md 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 3d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RunWhen Platform MCP Server — Copilot Instructions
This repository provides an MCP server for the RunWhen AI SRE platform. Use the MCP tools to investigate infrastructure, build automation tasks, and manage workspace configuration.
workspace_name is required
Most tools require a workspace_name parameter. Always provide it.
If unknown, call list_workspaces first.
Tool Routing
workspace_chat is the primary investigation tool — prefer it for any
question that involves searching, correlating, or interpreting infrastructure
data. It has internal semantic search, keyword grep, and resource graph
traversal that produce better answers than combining direct API calls.
Use direct tools only for: executing tasks (run_slx), task authoring
(validate_script, run_script_and_wait, commit_slx), registry
operations, chat config CRUD, KB mutations, and runner configuration.
Available Skills
This project includes detailed workflow skills in skills/ (also at .github/skills/).
Use these for multi-step tasks — they contain step-by-step instructions,
templates, and examples.
| Skill | When to use |
|---|---|
build-runwhen-task |
Building a new health check or automation task |
find-and-deploy-codebundle |
Deploying a pre-built codebundle from the registry |
run-existing-slx |
Running an existing SLX in a workspace |
verify-mcp-setup |
Validating the MCP server is installed and working |
create-ai-assistant |
Creating a new AI assistant (agent/persona) and tailoring it with rules and commands |
manage-rules |
Creating or updating workspace chat rules |
manage-commands |
Creating or updating workspace chat commands |
manage-knowledge |
Creating or updating knowledge base articles |
discover-secrets |
Finding available workspace secrets |
discover-locations |
Finding available runner locations |
configure-resource-path |
Setting resource paths for SLX indexing |
configure-hierarchy |
Organizing SLXs with hierarchy tags |
build-operational-context |
Building a RUNWHEN.md file for a project |
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.
- 3d ago First seen · 51 lines · 562 tokens per session scan A c94776bf1503
runwhen-platform-mcp copilot-instructions.md is an instructions file published in the GitHub repository runwhen-contrib/runwhen-platform-mcp (1 stars, last pushed 19d ago), licensed Apache-2.0. It adds 562 tokens to every session, about $0.0028 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 instructions, from other repositories
intervals-icu-mcp CLAUDE.md
Instructions for hhopke/intervals-icu-mcp, covering claude.md, project overview, development commands, architecture (quick reference) and tool categories.
flyto-core CLAUDE.md
Instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.
rosetta AGENTS.md
Instructions for tikoci/rosetta, covering codex instructions for rosetta, first reads, development defaults and mcp and client config.
pharo-smalltalk-interop-mcp-server CLAUDE.md
Instructions for mumez/pharo-smalltalk-interop-mcp-server, covering claude.md, project overview, development setup, environment variables and common commands.
rosetta llm-instruction-files-excluded-from-mdlint.instructions.md
LLM-targeted instruction files are excluded from markdownlint so authoring rules for human docs do not distort agent-facing guidance.
mcp-server-powerpoint code-review.instructions.md
Instructions for sbroenne/mcp-server-powerpoint, covering copilot code review, interop and resource safety, contract and path completeness and protocol, tests, and user-facing surfaces.