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 ABilenduke/copilot-developer --skill execute-plangit clone --depth 1 https://github.com/ABilenduke/copilot-developerWrote 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/abilenduke/copilot-developer/execute-plan)<a href="https://agentmods.dev/skills/abilenduke/copilot-developer/execute-plan"><img src="https://agentmods.dev/badge/skills/abilenduke/copilot-developer/execute-plan/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/abilenduke/copilot-developer/execute-plan"><img src="https://agentmods.dev/badge/skills/abilenduke/copilot-developer/execute-plan.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.00041 | $0.01271 |
| Opus 5.5 | $0.00016 | $0.00508 |
| Sonnet 5.5 | $0.00008 | $0.00254 |
| Haiku 4.5 | $0.00004 | $0.00127 |
Grade A, and why
execute-plan 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute Plan
Turn an existing plan into working, verified changes and a concise record another session can resume. Accept BRDs, conversation plans, ordinary Markdown, and usable legacy split documents. No companion skill, model, connector, catalog, or particular repository layout is required.
Respect mode and authorization
In native Plan Mode, perform only read-only readiness assessment and propose execution in the host's required chat format. Make no source, journal, or Git changes. An execution request does not change the active mode.
When implementation is allowed, work in the current checkout or existing worktree. Leave changes ready for review by default. Commits, pushes, PRs, ticket updates, and deployments follow explicit user instructions, including authorization already given. Preserve explicit review checkpoints; ordinary step boundaries do not require renewed permission.
Reconcile the plan with reality
- Use the explicitly supplied plan or the unambiguous plan in the conversation. Read referenced supporting documents only as needed. Ask which plan only if multiple plausible candidates remain; if none is available, request its location or content. Do not infer readiness from its filename, headings, directory, or status label.
- Identify requested behavior, acceptance criteria, dependency order, exclusions, and consequential decisions. Keep existing requirement IDs and delivery references. For plans without IDs, establish stable step references in the journal. A BRD's Ready status describes planning completeness, not authorization. A Discovery needed plan may authorize investigation while implementation remains blocked on specific decisions.
- Inspect applicable repository instructions, relevant implementation and tests, available check commands, and working tree and index changes before editing. Discover the actual stack. Record starting revision when available and baseline failures that affect later verification.
- Preserve unrelated edits and staged state. A dirty tree alone is not a blocker. Use isolation only when necessary; carry relevant context and changes deliberately without discarding the user's work. If overlapping changes make ownership or intended behavior unclear, resolve that specific gap.
- On resumption, read the existing journal and reconcile it with the latest plan, code, working tree, and check evidence. Recheck affected assumptions and stale results. Continue from the first unmet dependency; retain completed behavior and remove explicitly dropped scope from pending work. Read verification and resumption for drift or failures.
What ships with it
4 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.
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 · 103 lines · 41 tokens per session scan A d3370e026705
execute-plan is a skill published in the GitHub repository ABilenduke/copilot-developer (4 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 1,271 once invoked, about $0.0002 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-09-16.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…