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/verify-mcp-setupnpx skills add runwhen-contrib/runwhen-platform-mcp --skill verify-mcp-setupgit 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/verify-mcp-setup)<a href="https://agentmods.dev/skills/runwhen-contrib/runwhen-platform-mcp/verify-mcp-setup"><img src="https://agentmods.dev/badge/skills/runwhen-contrib/runwhen-platform-mcp/verify-mcp-setup.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.00101 | $0.01131 |
| Opus 5 | $0.00051 | $0.00566 |
| Sonnet 5 | $0.00020 | $0.00226 |
| Haiku 4.5 | $0.00010 | $0.00113 |
Grade A, and why
verify-mcp-setup 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 5d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify MCP Setup
Quick smoke test to confirm the RunWhen MCP server is connected, authenticated, and functional. Each step only checks for a valid response — it does NOT need to enumerate or display the returned data.
When to use
- First time connecting to a RunWhen MCP server
- After deploying or upgrading the server
- After changing environment variables (
RW_API_URL,RUNWHEN_TOKEN, etc.) - User asks to "verify", "validate", "test", or "check" the MCP connection
- Troubleshooting "tool not found" or timeout issues
Procedure
Run each step. Record PASS/FAIL/WARN. Do not stop on failure — finish all steps and present the summary at the end.
Step 1 — List workspaces (auth + connectivity)
Call list_workspaces().
- PASS: Returns a list with at least one workspace
- FAIL: Connection error → check
RW_API_URL; 401/403 → checkRUNWHEN_TOKEN
Pick a workspace for subsequent steps (use user-provided name, or the first returned).
Steps 2-5 — Read operations (batch in parallel)
Call all four in parallel with limit=1 where supported:
get_workspace_issues(workspace_name=WS, limit=1)get_workspace_slxs(workspace_name=WS)get_run_sessions(workspace_name=WS, limit=1)get_workspace_config_index(workspace_name=WS)
For each: PASS if valid JSON returned (empty results are fine). FAIL on 403/404/error.
Steps 6-7 — Runner infrastructure (batch in parallel)
get_workspace_locations(workspace_name=WS)— PASS if at least one location returned; WARN if emptyget_workspace_secrets(workspace_name=WS)— PASS if valid JSON; WARN if empty list
Steps 8-9 — Registry & validation (batch in parallel)
search_registry(search="kubernetes", max_results=1)— PASS if results returnedvalidate_script(script="def main():\n return []\n", interpreter="python", task_type="task")— PASS ifvalid: true
Steps 10-11 — Chat config (batch in parallel)
get_workspace_chat_config(workspace_name=WS)— PASS if valid JSON withrulesandcommandskeyslist_knowledge_base_articles(workspace_name=WS, limit=1)— PASS if valid JSON returned
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.
- 5d ago First seen · 114 lines · 101 tokens per session scan A 841f7ad499b7
verify-mcp-setup 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 101 tokens to every session and 1,131 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
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.
planning-and-task-breakdown
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.
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.