execute

A command that carries out an active step-by-step plan stored in a project's .claude/plans folder.

In plain words
What is it for?
Use it to run implementation plans one step at a time, verify each result, restart from a chosen step, or select among several active plans.
Why use it?
It prevents planned work from being marked complete without checking that each step worked, and stops when something fails.

Command

Install

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.

agentmods
npx agentmods add commands/ackeskin/contexture/execute
Clone the repo
git clone --depth 1 https://github.com/AcKeskin/contexture
Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 303 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00037 $0.00303
Opus 5 $0.00018 $0.00151
Sonnet 5 $0.00007 $0.00061
Haiku 4.5 $0.00004 $0.00030

Measured yesterday against content hash a9be2bb4f641, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

execute 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 yesterday.

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.

commands/execute.md · 19 lines

What it actually says

Run the execute skill.

Forms:

  • /execute (no slug) — resolve in this order: (1) if default is active in .claude/plans/INDEX.md, use it; (2) else if exactly one named active plan exists, use it; (3) else list active slugs and ask.
  • /execute <slug> — execute the active plan for <slug> (resolved from .claude/plans/INDEX.md).
  • /execute <slug> --from N — start from step N (skip earlier steps).
  • /execute <path> — explicit path to a specific plan version file (e.g. .claude/plans/auth-rework/v2.md). Bypasses INDEX. Useful for re-executing a superseded plan or running a draft plan.

Legacy fallback: if <slug> resolves to nothing AND $CLAUDE_PROJECT_DIR/PLAN.md exists at project root, the skill reads it with a one-time deprecation note.

Does not auto-fire. Verification evidence is required before each step is marked done. On verification failure, the skill stops and asks — no silent advance.

See ~/.claude/skills/execute/SKILL.md for the full procedure.

Changes

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.

  1. yesterday First seen · 19 lines · 37 tokens per session scan A a9be2bb4f641

Subscribe to this mod's changes

execute is a command published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 303 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.