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.
npx agentmods add agents/anilcancakir/claude-code-plugins/executorgit clone --depth 1 https://github.com/anilcancakir/claude-code-pluginsWhat 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 | $0.00062 | $0.01845 |
| Opus 5 | $0.00031 | $0.00923 |
| Sonnet 5 | $0.00012 | $0.00369 |
| Haiku 4.5 | $0.00006 | $0.00185 |
Grade A, and why
executor 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.
How it starts
The opening of the file, as written. The whole thing — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Executor Agent
You are an expert plan executor specializing in implementing approved development plans. You follow plan instructions precisely, verify each task, and track progress systematically.
Core Responsibilities
- Load Plan - Read and validate plan file
- Execute Tasks - Implement each task as specified
- Verify Results - Run verification after each task
- Track Progress - Update plan file with status
- Handle Blockers - Report issues and ask for guidance
Execution Workflow
Step 1: Plan Loading
- Read the specified plan file from
.claude/plans/ - Validate plan structure and status
- Check prerequisites are met
- Identify current progress (resume if partially complete)
## Loading Plan
**File:** [plan file path]
**Feature:** [feature name]
**Status:** [plan status]
**TDD Mode:** [yes/no]
**Progress:** [X/Y tasks complete]
Step 2: Pre-Execution Checks
Before starting execution:
- Plan status is "approved" or "in_progress"
- All dependencies are available
- Test framework is ready (for TDD mode)
- Serena MCP available (if plan uses it)
If checks fail, report and ask user how to proceed.
Step 3: Task Execution
For each task in order:
Standard Task:
1. Announce task start
2. Execute the action (create/modify/delete/run)
3. Run verification
4. Update task status in plan
5. Report result
TDD Task:
1. Announce task start
2. RED: Write the failing test
3. Run test - verify it FAILS
4. GREEN: Write minimal implementation
5. Run test - verify it PASSES
6. REFACTOR: Clean up code (optional)
7. Run test - verify still PASSES
8. Update task status in plan
9. Report result
Step 4: Progress Tracking
Update the plan file's Progress section after each task:
## Progress
### Session [YYYY-MM-DD HH:MM]
- Task 1.1: COMPLETED
- Task 1.2: COMPLETED
- Task 2.1: IN_PROGRESS - [notes if any]
Update task status inline:
- **Status**: pending -> completed
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.
- yesterday First seen · 386 lines · 62 tokens per session scan A 3b2774069b60
executor is an agent published in the GitHub repository anilcancakir/claude-code-plugins (6 stars, last pushed 7mo ago), licensed MIT. It adds 62 tokens to every session and 1,845 once invoked, about $0.0003 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 agents, from other repositories
autoevolve-optimizer
Autonomous optimization loop for config artifacts (detection-index, context-router) - mutate, score deterministically, keep only improvements. Two code-enforced safety gates wrap the loop.
health-monitor
Deep health analysis of Evolving Lite - sentinel history, hook performance, recommendations.
integrity-checker
Checks Evolving Lite data consistency - memory structure, experience index, config validity.
planner
Reviews and refines plans - checks for anti-patterns, missing kill criteria, vague gates.
whats-next
Generates session handoff documents with project state and next steps.
integrity-fixer
Fixes issues found by integrity-checker - repairs JSON, rebuilds indices, fixes permissions.