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 wiolett-industries/marketplace --skill executing-plansgit clone --depth 1 https://github.com/wiolett-industries/marketplaceWrote 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/wiolett-industries/marketplace/executing-plans)<a href="https://agentmods.dev/skills/wiolett-industries/marketplace/executing-plans"><img src="https://agentmods.dev/badge/skills/wiolett-industries/marketplace/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.00050 | $0.01032 |
| Opus 5 | $0.00025 | $0.00516 |
| Sonnet 5 | $0.00010 | $0.00206 |
| Haiku 4.5 | $0.00005 | $0.00103 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executing Plans
Execute the active plan as written. Plan artifacts are authoritative; chat is not. Inherit the primary path, assurance profile, task-wide agent budget, and verification budget from using-workflow.
Start Or Resume
- Call
workflow_statusonce when active state is unknown or context was recovered. - Read
manifest.json,state.json,plan.md, and the current task's referenced context/decisions. - Read
ui-contract.md, chunk state, or older artifacts only when the current task depends on them. - Inspect
git status --shortand preserve unrelated user changes. - Continue from the first non-complete task; do not replay completed work.
Use workflow_plan_update, workflow_plan_artifact_write, and workflow_plan_complete when available; manual state/artifact writes are fallback only.
Read references/execution-state.md only when updating task/chunk state, delegating a write task, or recovering a complex run.
Execution Cadence
- Update state at meaningful milestones: task start, material block, review handoff, and task completion.
- Do not write workflow state after every tool call or tiny edit.
- Execute tasks within their allowed scope and record any approved scope change before editing outside it.
- Do not perform opportunistic refactors. A new API/schema/protocol/shared abstraction/layer or a higher change class requires an approved plan update and a renewed commitment reflection before implementation continues.
- For production UI, read the UI contract's reuse receipt before markup/styles. Its exact labels are
Target:,Shared primitive:,Layout precedent:,Decision:,Structural verification:. Treat named reuse as architecture acceptance; stop before a local substitute, duplicate primitive, or unapproved layout deviation. - For a small user correction, inspect and edit only the touched surface plus directly affected tests; do not restart repository discovery.
- For chunks, root owns dependency order and integration. Never create nested chunks.
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.
- 2d ago Changed 8c483d5ba442
- 8d ago First seen · 69 lines · 50 tokens per session scan A 25ef700f5c7b
executing-plans is a skill published in the GitHub repository wiolett-industries/marketplace (10 stars, last pushed 3d ago), licensed MIT. It adds 50 tokens to every session and 1,032 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-30.
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…