Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add avmnu-sng/sutra/plugin install sutraWrote 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/avmnu-sng/sutra/scaffold-execution-plan)<a href="https://agentmods.dev/skills/avmnu-sng/sutra/scaffold-execution-plan"><img src="https://agentmods.dev/badge/skills/avmnu-sng/sutra/scaffold-execution-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/avmnu-sng/sutra/scaffold-execution-plan"><img src="https://agentmods.dev/badge/skills/avmnu-sng/sutra/scaffold-execution-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.00032 | $0.02588 |
| Opus 5 | $0.00016 | $0.01294 |
| Sonnet 5 | $0.00006 | $0.00518 |
| Haiku 4.5 | $0.00003 | $0.00259 |
Grade A, and why
scaffold-execution-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 9d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold execution plan
Lay down a durable, resumable structure for a build too large for one session, then wire in the build-orchestrator workflow that drives it. The structure is the source of truth across sessions: what to build next, in what order, and what "done" means for each unit of work.
This skill copies ready-made skeleton files that carry explicit TODO placeholders. It does not invent project specifics -- you (or a later planning pass) fill the placeholders against the real repo.
When to use
- A build that plausibly spans many sessions or many days.
- Work that decomposes into independent, shippable vertical slices.
- Any effort where "where did we leave off?" is a real cost and resume must be mechanical, not from memory.
When not to use
- A single-session change, a bug fix, or a one-slice feature. The overhead is not worth it.
- A repo that already has an
execution_plan/tree. Read it and resume instead of re-scaffolding (see Resume below).
Preconditions
- Run on a dedicated build branch or a worktree. NEVER scaffold or build on the default branch. Create the branch/worktree first.
- Confirm the repo root and the local fast-check command before writing
DEV_LOOP.md; if unknown, leave it as a TODO rather than guessing.
Step 0 -- adversarial pressure-test first
Before writing the plan, pressure-test the intended approach. The goal is
to surface the failure modes that a naive plan silently regresses on, then
encode each one as an explicit "do not regress" invariant in
MASTER_PLAN.md.
Walk these prompts and write down every real delta:
- Where does the naive slice ordering create a dependency cycle or force a big-bang integration at the end?
- Which slices share hidden state (a schema, a config file, a global) so that finishing them in the wrong order corrupts the other?
- What does each slice's acceptance criterion NOT catch? Name the class of bug that passes the criterion but breaks the system.
- Which "we will handle it later" is actually load-bearing now?
- What breaks under the real deployment/runtime conditions that a local run never exercises?
What ships with it
7 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.
- 9d ago First seen · 262 lines · 32 tokens per session scan A c4d768346ad2
scaffold-execution-plan is a skill published in the GitHub repository avmnu-sng/sutra (2 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 2,588 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
memstack-business-client-onboarding
Use this skill when the user says 'client onboarding', 'new client', 'onboard client', 'kickoff meeting', 'intake form', 'welcome email', or needs welcome sequences, questionnaires, and setup checklists for new clients. Do NOT use for contracts or invoicing.
memstack-product-roadmap-builder
Use this skill when the user says 'roadmap', 'product roadmap', 'quarterly plan', 'now/next/later', 'OKRs', or needs strategic planning with themes, milestones, resource allocation, and stakeholder-ready views. Do NOT use for MVP scoping or sprint-level planning.
memstack-product-mvp-scoper
Use this skill when the user says 'MVP', 'minimum viable product', 'scope the MVP', 'what should I build first', 'strip to core', or needs to define the smallest build that validates a product hypothesis. Do NOT use for full PRDs or roadmap planning.
memstack-product-user-story-generator
Use this skill when the user says 'user stories', 'write stories', 'backlog', 'sprint planning', 'acceptance criteria', or needs prioritized stories with Given/When/Then criteria and story point estimates. Do NOT use for full PRDs or detailed feature specs.
memstack-marketing-marketplace-submit
Use when the user says 'submit to marketplace', 'publish my skill', 'share this skill', 'list on marketplace', 'submit plugin', 'publish to community', or needs to submit a skill or plugin to a community marketplace via PR. Do NOT use for building skills or writing plugin code.
state
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.