execute

A command that carries out an existing development plan using TDD, or test-driven development: write a failing test, make it pass with the smallest change, then improve the code. It can continue from the last unfinished test case.

In plain words
What is it for?
Use it to implement planned features one test case at a time, run the planned checks, and continue unfinished work from a saved plan.
Why use it?
It turns a written plan into tracked implementation work and lets interrupted development resume without starting over.

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/ruslan-korneev/claude-plugins/execute
Clone the repo
git clone --depth 1 https://github.com/ruslan-korneev/claude-plugins
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,412 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.00022 $0.01412
Opus 5 $0.00011 $0.00706
Sonnet 5 $0.00004 $0.00282
Haiku 4.5 $0.00002 $0.00141

Measured 2d ago against content hash a475b493a76d, 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 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.

plugins/tech-lead/commands/execute.md · 249 lines

How it starts

The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Execute Plan Command

Execute an existing development plan using TDD methodology. Supports resuming interrupted work.

Workflow

┌─────────────────────────────────────────────────────────────────┐
│               /dev:execute ".claude/plans/dev-{slug}.md"        │
└─────────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────────┐
│ PHASE 1: LOAD PLAN                                              │
│                                                                 │
│ - Read plan file                                                │
│ - Parse test cases                                              │
│ - Find first uncompleted [  ] test case                         │
│ - Load memory anchors for context                               │
└─────────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────────┐
│ PHASE 2: TDD EXECUTION                                          │
│                                                                 │
│ For each uncompleted test case:                                 │
│                                                                 │
│ ┌─────────┐    ┌─────────┐    ┌───────────┐                    │
│ │   RED   │───▶│  GREEN  │───▶│ REFACTOR  │                    │
│ │ Failing │    │  Pass   │    │  Quality  │                    │
│ │  Test   │    │  Test   │    │   Check   │                    │
│ └─────────┘    └─────────┘    └───────────┘                    │
│                                                                 │
│ Plugins used:                                                   │
│ - pytest-assistant:first (RED)                                  │
│ - clean-code:review (REFACTOR)                                  │
│ - ruff-lint hooks (auto)                                        │
│ - python-typing hooks (auto)                                    │
└─────────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────────┐
│ PHASE 3: COMPLETION                                             │
│                                                                 │
│ - Run full test suite                                           │
│ - Verify quality gates                                          │
│ - Update plan status to "completed"                             │
│ - Suggest commit message                                        │
└─────────────────────────────────────────────────────────────────┘

Read the full file on GitHub · 249 lines

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. 2d ago First seen · 249 lines · 22 tokens per session scan A a475b493a76d

Subscribe to this mod's changes

execute is a command published in the GitHub repository ruslan-korneev/claude-plugins (4 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 1,412 once invoked, about $0.0001 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.