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.
git clone --depth 1 https://github.com/ruslan-korneev/claude-pluginsWrote 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/commands/ruslan-korneev/claude-plugins/execute)<a href="https://agentmods.dev/commands/ruslan-korneev/claude-plugins/execute"><img src="https://agentmods.dev/badge/commands/ruslan-korneev/claude-plugins/execute/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/commands/ruslan-korneev/claude-plugins/execute"><img src="https://agentmods.dev/badge/commands/ruslan-korneev/claude-plugins/execute.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.00022 | $0.01412 |
| Opus 5.5 | $0.00009 | $0.00565 |
| Sonnet 5.5 | $0.00004 | $0.00282 |
| Haiku 4.5 | $0.00002 | $0.00141 |
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 1mo 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 — 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 │
└─────────────────────────────────────────────────────────────────┘
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.
- 1mo ago First seen · 249 lines · 22 tokens per session scan A a475b493a76d
execute is a command published in the GitHub repository ruslan-korneev/claude-plugins (5 stars, last pushed 7mo ago), licensed MIT. It adds 22 tokens to every session and 1,412 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
test-skill
Test Claude Code skills using RED/GREEN/REFACTOR TDD phases in fresh subagents to prevent priming bias.
symfony-tdd-pest
Start a TDD workflow using Pest PHP for Symfony with RED-GREEN-REFACTOR cycle.
atdd
Start the ATDD workflow for a new feature. Optionally provide a feature description as an argument.
bugfix
TDD-driven bugfix workflow: tester writes failing test (RED) → developer fixes (GREEN) → developer refactors (REFACTOR) → reviewer validates. Accepts issue number, description, or both. Asks before pushing and creating a PR; --no-pr commits locally without asking.
loop
Autonomous execution loop. Runs the TDD cycle repeatedly until all tasks in an epic are complete, with circuit breaker protection and PR workflow.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.