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/xinghang-ee-cs/dev-runtime-skill/planning-layer-runtimenpx skills add xinghang-ee-cs/dev-runtime-skill --skill planning-layer-runtimegit clone --depth 1 https://github.com/xinghang-ee-cs/dev-runtime-skillWhat 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.00251 | $0.05539 |
| Opus 5 | $0.00125 | $0.02769 |
| Sonnet 5 | $0.00050 | $0.01108 |
| Haiku 4.5 | $0.00025 | $0.00554 |
Grade A, and why
planning-layer-runtime 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What ships with it
17 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 1.4 KB
- references/00-planning-user-discovery.md 26 KB
- references/01-planning-core-rules.md 25 KB
- references/02-planning-change-levels.md 9.5 KB
- references/03-planning-doc-responsibility.md 47 KB
- references/04-planning-format-spec.md 99 KB
- references/05-planning-priority-system.md 5.7 KB
- references/06-planning-capability-governance.md 22 KB
- references/07-planning-conversation-runtime.md 108 KB
- references/08-planning-recovery-runtime.md 31 KB
- references/09-execution-intent-guard.md 4.5 KB
- references/10-planning-document-interaction-runtime.md 53 KB
- references/11-planning-ui-ux-execution-contract.md 23 KB
- references/12-planning-ui-ux-execution-example.md 18 KB
- references/13-planning-database-persistence-contract.md 15 KB
- scripts/validate_database_persistence_contract.py 6.8 KB runs code
- scripts/validate_ui_ux_contract.py 24 KB runs code
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 · 324 lines · 251 tokens per session scan A 8c4165bc8668
planning-layer-runtime is a skill published in the GitHub repository xinghang-ee-cs/dev-runtime-skill (9 stars, last pushed 9d ago), licensed AGPL-3.0. It adds 251 tokens to every session and 5,539 once invoked, about $0.0013 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.