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-hierarchygit 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-hierarchy)<a href="https://agentmods.dev/skills/runwhen-contrib/runwhen-platform-mcp/configure-hierarchy"><img src="https://agentmods.dev/badge/skills/runwhen-contrib/runwhen-platform-mcp/configure-hierarchy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/runwhen-contrib/runwhen-platform-mcp/configure-hierarchy"><img src="https://agentmods.dev/badge/skills/runwhen-contrib/runwhen-platform-mcp/configure-hierarchy.svg" alt="Reviewed on agentmods" width="80" 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.00091 | $0.01139 |
| Opus 5 | $0.00046 | $0.00570 |
| Sonnet 5 | $0.00018 | $0.00228 |
| Haiku 4.5 | $0.00009 | $0.00114 |
Grade A, and why
configure-hierarchy 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 8d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure Hierarchy
Sets spec.additionalContext.hierarchy on an SLX to define how it is grouped in the workspace UI and how legacy path construction works from tags.
What hierarchy does
hierarchy is a list of tag names that defines the nesting order for an SLX. The platform reads each tag name in the hierarchy, looks up its value from spec.tags, and uses the values to build a grouping path.
Example: hierarchy ["cluster", "namespace", "resource_name"] with tags cluster=cluster-01, namespace=prod, resource_name=papi produces grouping path cluster-01/prod/papi.
How it relates to resourcePath
| Field | Purpose | Source |
|---|---|---|
resourcePath |
Canonical search/indexing path (includes custom/ platform prefix for MCP tasks) |
Set directly as a string |
hierarchy |
UI grouping; legacy path construction (no platform prefix) | List of tag names, values resolved from tags |
Both live under spec.additionalContext. Always set both for full functionality. The resourcePath is the primary identifier for search; hierarchy controls the UI grouping.
Important: For MCP-authored tasks, resourcePath must always start with custom/ (the server enforces this automatically). The hierarchy defines the grouping within the custom tree. Always include "platform" as the first hierarchy entry with a tag value of "custom" so that the UI groups these tasks under the custom namespace.
Format
A YAML list of tag names that exist in spec.tags. For MCP-authored tasks, always start with platform=custom:
spec:
tags:
- name: platform
value: custom
- name: resource_type
value: platform
- name: resource_name
value: papi-issues
additionalContext:
resourcePath: custom/runwhen/papi
hierarchy:
- platform
- resource_type
- resource_name
Common hierarchy patterns
All MCP-authored tasks should start the hierarchy with platform → custom.
Custom Kubernetes task
hierarchy:
- platform
- cluster
- namespace
- resource_name
Tags: platform=custom, cluster=cluster-01, namespace=backend-services, resource_name=papi
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.
- 8d ago First seen · 121 lines · 91 tokens per session scan A e1e7ba75ba1c
configure-hierarchy is a skill published in the GitHub repository runwhen-contrib/runwhen-platform-mcp (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 91 tokens to every session and 1,139 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
daily-briefing
Start your day with a prioritized CRM briefing — works for any monday CRM setup: pipeline, contacts, accounts, leads, or no board at all. Use when someone says 'morning briefing', 'daily brief', 'what's on my plate today', 'catch me up on my deals', 'what needs attention', 'what needs my attention', 'anything urgent…
meeting-to-deal
Turn meeting transcripts into deal updates — key points, commitments, and next steps posted to matching CRM deals automatically. Auto-creates contacts for new attendees. Use when someone says "log my meetings to deals", "update CRM from calls", "what did I commit to in meetings", "sync notetaker", "log this meeting"…
log-activity
Log calls, meetings, notes, and other activities to CRM item timelines — structured records with attendees, outcomes, and follow-ups. Use when someone says "log my call with", "add a note to the deal", "what activities happened on", "record this meeting", "update my note on", "track a call with", "log a meeting with"…
Technical Debt Tracking with PMAT
Tracks and manages technical debt using PMAT (Pragmatic AI Labs MCP Agent Toolkit). Use this skill when: User asks about technical debt, TODO comments, or code quality issues Planning sprint work and need to prioritize debt repayment Conducting code audits or technical debt assessments Tracking debt accumulation…
pipefy-pipes-and-cards
Use this skill when the user wants to read, create, update, or delete pipes, phases, phase fields, labels, cards, comments, or field conditions. Covers 40 MCP tools for the core pipe and card lifecycle. Use the seed-pipe-across-phases workflow when populating empty phases for demos or QA.
pipefy-process-design
Use this skill ONLY when the user explicitly asks for help designing or architecting a process ("help me design", "what's the best structure", "how do I organize this flow?"). For direct execution requests ("create a pipe for X", "build a reimbursement process", or any message with a detailed spec), skip this skill…