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/commit-to-codecollectionnpx skills add runwhen-contrib/runwhen-platform-mcp --skill commit-to-codecollectiongit clone --depth 1 https://github.com/runwhen-contrib/runwhen-platform-mcpWhat 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.00130 | $0.03459 |
| Opus 5 | $0.00065 | $0.01729 |
| Sonnet 5 | $0.00026 | $0.00692 |
| Haiku 4.5 | $0.00013 | $0.00346 |
Grade A, and why
commit-to-codecollection 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 2d 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 — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit to CodeCollection (GitOps)
Render a tested tool-builder task into the Custom Discovery CodeCollection layout documented at https://docs.runwhen.com/guides/custom-discovery-codecollection/
This is the GitOps alternative to commit_slx (which writes inline scripts into the workspace repo).
When to use each path
| Goal | Tool |
|---|---|
| Fast iteration in a dev workspace | commit_slx |
| Version-controlled, reusable bundle in your git repo | render_codecollection_skill |
| Deploy a registry Skill Template | deploy_registry_codebundle |
Prerequisites
- Task already tested via
run_script_and_wait(same bar ascommit_slx) get_workspace_contextloaded before authoring- Platform format confirmed with the user (see below)
- runwhen-local release with the matching platform indexer on the target runner
platform: runwhen→ RW-1355 runwhen indexerplatform: kubernetes|azure|aws|gcp→ that cloud indexer enabled inworkspaceInfo.yaml
Choose output format (ask the user first)
Do not call render_codecollection_skill until the user confirms platform and scope.
- Call
list_discovery_platforms()and present the two main paths:
| User goal | platform |
Typical scope |
|---|---|---|
| One health-check SLX for the whole workspace (MCP tool-builder) | runwhen |
resource_types: [workspace] |
| One SLX per K8s namespace/deployment/CRD/etc. | kubernetes |
e.g. [namespace], [deployment] |
| One SLX per Azure/AWS/GCP resource | azure / aws / gcp |
CloudQuery table names from catalog |
-
Ask clarifying questions when ambiguous:
- "Should this run once per workspace, or once per Kubernetes namespace/cluster/resource?"
- "Which cloud account scope — individual resources, resource groups, or subscriptions?"
- For Kubernetes: "Which namespace pattern or resource type should drive SLX creation?"
-
Call
list_indexed_resource_types(platform=<chosen>, search=<hint>)and only offerresource_typesvalues returned by that tool (plus Kubernetes CRDplural.group[/version]syntax when the user names a CRD).
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.
- 2d ago First seen · 304 lines · 130 tokens per session scan A 59fd42c9c2ba
commit-to-codecollection is a skill published in the GitHub repository runwhen-contrib/runwhen-platform-mcp (1 stars, last pushed 19d ago), licensed Apache-2.0. It adds 130 tokens to every session and 3,459 once invoked, about $0.0006 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…
xcodebuildmcp-structured-output-review
Use when reviewing XcodeBuildMCP structured output schema changes, schema versioning, manifest outputSchema metadata, and JSON fixture compatibility.
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — errors, failed tool calls, latency, regressions, and low online-eval scores — plus Diagnostics issues. Reads live/production traces via the SDK (searchtraces and agentinsights) and works with no MCP; uses the MCP issue entity when connected.…
mcp-transport-contract-auditor
Route shaft-mcp transport-contract audits to the canonical playbook.
create-operator
MUST READ before creating or moving any operator (createop, copyop, setopposition, or executepython builds). Required verification, canonical positioning recipe, and error-checking steps.
cortex-automate
Set up automation — prospective memory triggers, neuro-symbolic rules, and CLAUDE.md sync. Use when the user says 'remind me when', 'trigger when', 'create a rule', 'auto-remember', 'sync to CLAUDE.md', 'push insights', 'set up trigger', 'when I open this file', 'when this keyword appears', or when you want to…