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 Eilodon/DPS-Superskills-MCP --skill executing-plansgit clone --depth 1 https://github.com/Eilodon/DPS-Superskills-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/eilodon/dps-superskills-mcp/executing-plans)<a href="https://agentmods.dev/skills/eilodon/dps-superskills-mcp/executing-plans"><img src="https://agentmods.dev/badge/skills/eilodon/dps-superskills-mcp/executing-plans.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.00033 | $0.00593 |
| Opus 5 | $0.00016 | $0.00296 |
| Sonnet 5 | $0.00007 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
executing-plans 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executing Plans
Load plan, review critically, execute all tasks with verification at each step, finish with adr-commit.
Prefer subagent-driven-development if your harness supports subagents.
Executing-plans is for environments where subagent dispatch is not available.
Announce: "Using executing-plans to implement this plan."
Step 1: Load and Review Plan
- Read plan file from
docs/superskills/plans/ - Review critically — identify questions or concerns
- If concerns → raise with human before starting
- If no concerns → create TodoWrite and proceed
Step 2: Execute Tasks
For each task:
- Mark as
in_progressin TodoWrite - Follow each step exactly — plan has exact code and commands
- For each code step: use
tdd-verified(write test → watch fail → implement → watch pass) - Run verifications as specified
- After confirmed bug fix → trigger
pattern-globalize - Before marking done → run
verification-before-completion - Mark as
completed
Step 3: Finish with adr-commit
After all tasks complete:
- Announce: "Using adr-commit to complete this work."
- Invoke
adr-commit— ADR Gate + G.CDOC + PATTERN-DEBT lifecycle + merge options
Do NOT use finishing-a-development-branch. Use adr-commit.
When to Stop
Stop immediately when:
- Blocker that prevents continuing (missing dependency, repeated test failure)
- Plan has critical gaps preventing starting
- Instruction unclear
- Verification fails repeatedly
Ask for clarification. Do not guess through blockers.
Key Rules
- Review plan critically before starting
- Follow plan steps exactly — do not improvise
- Do not skip verifications
- Stop when blocked, ask for direction
- Never start on main/master without explicit user consent
tdd-verifiedfor every implementation steppattern-globalizeafter every confirmed bugverification-before-completionbefore every "task complete" mark
Gotchas — Observed Failure Points
What ships with it
1 file 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.
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 · 79 lines · 33 tokens per session scan A bba7c9ec81ec
executing-plans is a skill published in the GitHub repository Eilodon/DPS-Superskills-MCP (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 593 once invoked, about $0.0002 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…