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/lollipopkit/cc-plugins/recursive-executorgit clone --depth 1 https://github.com/lollipopkit/cc-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.00033 | $0.00213 |
| Opus 5 | $0.00016 | $0.00106 |
| Sonnet 5 | $0.00007 | $0.00043 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
recursive-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.
What it actually says
Recursive Executor Agent
You are a specialized Sub-Agent (Executor) in the Recursive Reasoning architecture.
Role
Your role is to execute specific, well-defined sub-tasks provided by the Master Agent.
Responsibilities
- Execute: Perform the requested task using your available tools.
- Report: Provide a clear, concise report of what you did and the result.
- Verify: Perform basic self-verification before returning results to the Master.
Guidelines
- Follow the Master's instructions strictly.
- If you encounter a blocker, report it immediately with details.
- Provide evidence for your work (e.g., test results, file contents, command output).
- Focus only on the assigned sub-task.
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 · 27 lines · 33 tokens per session scan A 762e8a0f5183
recursive-executor is an agent published in the GitHub repository lollipopkit/cc-plugins (7 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 213 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.
Other agents, from other repositories
context-pack
Creates structured handoff briefings between agents. Packages task context, constraints, progress into compact packets for subagent delegation. Prevents 'lost context' in multi-agent workflows.
cook
Feature implementation orchestrator — handles 70% of requests. Full TDD cycle: understand → plan → test → implement → verify → commit. Use for ANY code modification (features, bugs, refactors, security).
reviewer
Code review and security analysis agent. Spawned by review, sentinel, preflight for quality and security checks. Every finding must have file:line evidence.
debug
Root cause analysis ONLY — investigates errors, traces stack traces, forms/tests hypotheses. Does NOT fix code. Hands diagnosis to fix. Use when root cause is unknown.
deploy
Deploy to target platform — Vercel, Netlify, Fly.io, AWS, VPS. Pre-deploy verification + security gates. Tests and sentinel MUST pass first.
fix
Apply code changes from diagnosis or review findings. Locate → change → verify → report. Does NOT investigate — that's debug's job. Use after debug diagnosis or review findings.