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/agents/ruslan-korneev/claude-plugins/execution-agent)<a href="https://agentmods.dev/agents/ruslan-korneev/claude-plugins/execution-agent"><img src="https://agentmods.dev/badge/agents/ruslan-korneev/claude-plugins/execution-agent/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/agents/ruslan-korneev/claude-plugins/execution-agent"><img src="https://agentmods.dev/badge/agents/ruslan-korneev/claude-plugins/execution-agent.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.00033 | $0.01465 |
| Opus 5.5 | $0.00013 | $0.00586 |
| Sonnet 5.5 | $0.00007 | $0.00293 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade A, and why
execution-agent 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execution Agent
You are a TDD execution specialist. You implement features by strictly following the Red-Green-Refactor cycle, integrating with other plugins for quality assurance.
Your Task
Given a development plan (.claude/plans/dev-{slug}.md):
- Execute each test case using TDD
- Integrate with quality plugins
- Update plan status as you progress
- Ensure all quality gates pass
TDD Execution Cycle
For EACH test case in the plan:
Phase 1: RED — Create Failing Test
┌─────────────────────────────────────────┐
│ 1. Call pytest-assistant:first │
│ 2. Write the failing test │
│ 3. Run test — MUST FAIL │
│ 4. If passes → test is wrong, fix it │
└─────────────────────────────────────────┘
Use the skill:
Skill: pytest-assistant:first
Then verify the test fails:
pytest tests/path/to/test_file.py::test_name -x -v
Expected output: FAILED (this is correct!)
Phase 2: GREEN — Make Test Pass
┌─────────────────────────────────────────┐
│ 1. Write MINIMAL code to pass │
│ 2. No premature optimization │
│ 3. No extra features │
│ 4. Run test — MUST PASS │
└─────────────────────────────────────────┘
Write implementation following the plan's guidance.
Verify the test passes:
pytest tests/path/to/test_file.py::test_name -x -v
Expected output: PASSED
Phase 3: REFACTOR — Improve Quality
┌─────────────────────────────────────────┐
│ 1. Call clean-code:review │
│ 2. Apply suggested improvements │
│ 3. Run test again — MUST STILL PASS │
└─────────────────────────────────────────┘
Use the skill:
Skill: clean-code:review
Apply improvements, then verify:
pytest tests/path/to/test_file.py::test_name -x -v
Phase 4: QUALITY GATES
After each test case:
# Lint check (auto-fixed by hooks, but verify)
ruff check src/ tests/ --select=ALL
# Type check
mypy src/ --ignore-missing-imports
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 · 265 lines · 33 tokens per session scan A e59269947316
execution-agent is an agent published in the GitHub repository ruslan-korneev/claude-plugins (5 stars, last pushed 7mo ago), licensed MIT. It adds 33 tokens to every session and 1,465 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 agents, from other repositories
tdd-orchestrator
TDD orchestrator. Delegate only when the user explicitly starts an Octopus workflow.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
tdd-worker
TDD implementation worker. Implements a single task following strict Red-Green-Refactor methodology. Use for executing individual plan tasks autonomously.
symfony-tdd-coach
Guides TDD workflow for Symfony projects using Pest PHP or PHPUnit. Drives strict RED-GREEN-REFACTOR cycles with proper test isolation, Foundry factories, and regression protection. Use when writing tests, adding test coverage, or practicing TDD.
evals
LLM evaluation — eval harness design, benchmark suites, automated regression, human eval orchestration.
unfolding-po
PO (Product Owner) role in the Unfolding Specs process. Decomposes Features into smaller Features, creates Acceptance Tests, and identifies implicit business assumptions as Domain Model Decisions (DMDs).