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 skills add runwhen-contrib/runwhen-platform-mcp --skill configure-resource-pathgit 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/configure-resource-path)<a href="https://agentmods.dev/skills/runwhen-contrib/runwhen-platform-mcp/configure-resource-path"><img src="https://agentmods.dev/badge/skills/runwhen-contrib/runwhen-platform-mcp/configure-resource-path.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.00088 | $0.01071 |
| Opus 5 | $0.00044 | $0.00535 |
| Sonnet 5 | $0.00018 | $0.00214 |
| Haiku 4.5 | $0.00009 | $0.00107 |
Grade A, and why
configure-resource-path 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure Resource Path
Sets spec.additionalContext.resourcePath on an SLX so workspace-chat and usearch can discover and group tasks by infrastructure location.
What resourcePath does
resourcePath is the canonical identifier for where an SLX's target resource lives. It controls:
- How workspace-chat finds and routes questions to relevant tasks
- How usearch indexes SLXs for keyword and semantic search
- How the UI groups SLXs by infrastructure location
Format
A forward-slash-separated path, platform prefix first, then narrowing to the specific resource:
<platform>/<level-1>/<level-2>/.../<resource>
CRITICAL: Custom tasks MUST use the custom/ platform prefix
Tasks built via the MCP server (commit_slx or deploy_registry_codebundle) are custom tasks — they must never share a resourcePath with existing platform-managed resources. The MCP server enforces this automatically:
- All resource paths are prefixed with
custom/— if you passkubernetes/cluster-01/ns, the server rewrites it tocustom/kubernetes/cluster-01/ns - If you already include
custom/, the path is left unchanged - This prevents custom tasks from appearing under the same grouping as platform-discovered resources
Why this matters
Platform-managed resources (discovered by runwhen-local, Crossplane, etc.) own their resource paths. If a custom task uses the same path, it pollutes the resource tree and creates confusing groupings in the UI and search results. The custom/ prefix keeps MCP-authored tasks in their own namespace.
Examples by platform
| Platform | resourcePath | Description |
|---|---|---|
| Custom (MCP-authored) | custom/kubernetes/cluster-01/namespace-a/papi |
Custom task targeting a K8s deployment |
| Custom (MCP-authored) | custom/aws/us-east-1/lambda/my-function |
Custom task targeting a Lambda function |
| Custom (MCP-authored) | custom/github |
Custom task for GitHub operations |
| Custom (MCP-authored) | custom/runwhen/papi |
Custom task for RunWhen platform |
| Custom (MCP-authored) | custom/gcp/project-x/gke/cluster-01 |
Custom task targeting a GKE cluster |
| Platform-managed | kubernetes/cluster-01/kube-system |
Discovered by runwhen-local (NOT for custom tasks) |
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 · 84 lines · 88 tokens per session scan A 131fc540f84e
configure-resource-path is a skill published in the GitHub repository runwhen-contrib/runwhen-platform-mcp (1 stars, last pushed 23d ago), licensed Apache-2.0. It adds 88 tokens to every session and 1,071 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.
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.
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…