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 ayberkcansever/ai-skills --skill execute-plangit clone --depth 1 https://github.com/ayberkcansever/ai-skillsWrote 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/ayberkcansever/ai-skills/execute-plan)<a href="https://agentmods.dev/skills/ayberkcansever/ai-skills/execute-plan"><img src="https://agentmods.dev/badge/skills/ayberkcansever/ai-skills/execute-plan.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.00057 | $0.05327 |
| Opus 5 | $0.00028 | $0.02663 |
| Sonnet 5 | $0.00011 | $0.01065 |
| Haiku 4.5 | $0.00006 | $0.00533 |
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 3d 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 — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute Plan
Overview
Load plan, review critically, execute ready tasks in waves in the ticket venue (this checkout if already on the ticket branch, else a worktree), run the verifications the plan specifies, report when complete.
Announce at start: "I'm using the execute-plan skill to implement this plan."
The Process
Step 1: Load and Review Plan
- Read the plan file (the one produced by write-plan or interview-plan).
Infer
<TICKET-ID>from the plan path first, then an existing ticket worktree, then the current branch, then ask once — the user's checkout may be onmainor another ticket. If the user did not say which file, search in this order:- already-listed worktree for this ticket (it is live — prefer it)
docs/features/<TICKET-ID>/(tracked)docs/plans/<TICKET-ID>/(gitignored WIP)- Legacy flat
docs/plans/*.mdordocs/PLAN_*.mdIf both tracked and WIP copies exist in the same checkout, diff them; if they diverge, ask which is active — never silently prefer the promoted copy over newer WIP. Record the absolute path of the user's checkout — Step 2 copies from there only when the worktree does not already have the WIP docs.
- Review it critically — identify any questions, gaps, or concerns before
touching code. A plan whose header links a spec but carries no
**Audit:** cleanline: if an interview spec exists for this ticket, the Audit Pass was interrupted — confirm before executing. If there was no interview (standalone write-plan), missing audit is expected — still confirm once, then proceed. Do not treat both cases as "interrupted interview". - If concerns: raise them with the user before starting. Resume / stash / TodoWrite wait until Step 2 has the live plan.
Step 2: Open the execution venue
Already on this ticket's branch (git branch --show-current contains
<TICKET-ID>): this checkout is the venue. Skip git-worktrees. Skip the
WIP copy below. Git will not attach the same branch in a second worktree —
stay here instead of deadlocking.
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.
- 3d ago Changed · +3 lines 1bb607180635
- 8d ago First seen · 390 lines · 57 tokens per session scan A 2ff716c86cac
execute-plan is a skill published in the GitHub repository ayberkcansever/ai-skills (2 stars, last pushed 4d ago), licensed MIT. It adds 57 tokens to every session and 5,327 once invoked, about $0.0003 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
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
ijfw-workflow
Use when the user says: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', 'launch', 'book', 'campaign', or anything project-level. Skill body decides Quick vs Deep path.
ijfw-plan
Use when the user says 'plan this', 'plan it', 'make a plan', 'let's plan', 'draft a plan', 'how should we tackle this', 'break this down', or invokes '/ijfw-plan'. Produces a falsifiable PLAN.md (software, book, campaign, design, research) with task breakdown, dependency wave-table, and success criteria — gated by…
ijfw-milestone-summary
Use when the user asks for a milestone summary, milestone recap, or to summarize a milestone -- or runs /ijfw-milestone-summary. Trigger: 'milestone summary', 'summarize milestone', 'milestone recap', 'onboard someone to this release', 'what shipped in v ', invoked by ijfw-complete-milestone.