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 andreaswasita/copilot-agents-dojo --skill executing-plansgit clone --depth 1 https://github.com/andreaswasita/copilot-agents-dojoWrote 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/andreaswasita/copilot-agents-dojo/executing-plans)<a href="https://agentmods.dev/skills/andreaswasita/copilot-agents-dojo/executing-plans"><img src="https://agentmods.dev/badge/skills/andreaswasita/copilot-agents-dojo/executing-plans/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/andreaswasita/copilot-agents-dojo/executing-plans"><img src="https://agentmods.dev/badge/skills/andreaswasita/copilot-agents-dojo/executing-plans.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00017 | $0.01071 |
| Opus 5.5 | $0.00007 | $0.00428 |
| Sonnet 5.5 | $0.00003 | $0.00214 |
| Haiku 4.5 | $0.00002 | $0.00107 |
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 1mo 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executing Plans Skill
Walks an approved tasks/todo.md plan step by step: pick the next task, execute it, verify it, commit it, mark it done. Does NOT freelance new scope mid-execution and does NOT skip the verification gate.
When to Use
- A plan in
tasks/todo.mdhas been approved. - Starting or resuming a multi-step implementation.
- User says "go", "start", "execute", or "begin".
- A sub-agent batch finishes and the next batch is ready.
- NOT before the design is approved (use
brainstormingfirst).
Prerequisites
- Approved
tasks/todo.mdcontaining ordered steps with acceptance criteria. gitconfigured for atomic commits.- The
view,edit, andpowershellCopilot tools. - A green baseline test run.
- The
verify-before-doneskill available for the verification step.
How to Run
1. Read tasks/todo.md. Identify the next unchecked task.
2. Confirm its prerequisites are satisfied.
3. Execute the task.
4. Run the verify-before-done skill.
5. Append the Verification Results block.
6. Commit. Mark the checkbox `- [x]`.
7. Repeat. Post a short progress note every 2–3 tasks.
Quick Reference
| Phase | Action | Tool |
|---|---|---|
| Load | Read tasks/todo.md |
view |
| Execute | Make the change | edit, powershell |
| Verify | Tests + gate + diff | verify-before-done skill |
| Record | Append Verification Results | edit |
| Commit | One commit per task | powershell → git commit |
| Mark done | Flip - [ ] to - [x] |
edit |
Procedure
Step 1: Load the Plan
Open tasks/todo.md with view. Locate the next - [ ] step. If none exist, the plan is done — hand off to finishing-a-development-branch.
Step 2: Check Prerequisites
Read the task. Confirm any "depends on" notes are satisfied. If a prerequisite is missing, STOP — do not improvise around it; re-plan first.
Step 3: Execute Exactly One Task
Make the change. Resist the urge to bundle "while I'm here" cleanups. Scope discipline is the whole point of the plan.
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.
- 1mo ago First seen · 130 lines · 17 tokens per session scan A b01bb714e85d
executing-plans is a skill published in the GitHub repository andreaswasita/copilot-agents-dojo (54 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 1,071 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
plan
Use when an approved, clarified spec must become a technical blueprint before any code — the SDD phase between clarify and tasks: architecture, contracts, data flow, testing strategy, sequencing and risks, at structure altitude, never framework syntax. NOT the what/why spec (that is specify), NOT the ambiguity sweep…
Workflow Automation
Break a multi-step goal into execution stages, map those stages to Home23 tools and skills, and set safe execution order.
decision-ledger
A session record for tracking unresolved decisions and drafting them into `.governance/claims/` when they are settled. It preserves both the decision and the reason behind it.
governance-bootstrap
A guided checklist for creating a project's governance system from scratch when no governance exists.
session-grounding
A session-start procedure for checking the current facts, scope, and work track in a governed project before taking action.
truth-first
A set of rules for writing technical conclusions and performing irreversible or state-changing operations. It requires evidence tied to file and line locations and restricts unsupported claims.