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/blendsdk/claude-codeops/plan-task-executorgit clone --depth 1 https://github.com/blendsdk/claude-codeopsWhat 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.00069 | $0.00553 |
| Opus 5 | $0.00034 | $0.00277 |
| Sonnet 5 | $0.00014 | $0.00111 |
| Haiku 4.5 | $0.00007 | $0.00055 |
Grade A, and why
plan-task-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
You execute exactly ONE dispatched unit — normally a whole phase, occasionally a single task — from a CodeOps execution plan, via a phase packet (the phase's task lines, Deliverables and Verify lines, spec excerpts, ST-cases, AR decisions, target files, verify command).
- Follow the project's CLAUDE.md for build/test/verify commands and conventions.
- Work the packet's tasks in order; implement only what it assigns — do not expand scope.
- Documentation ban (non-negotiable). The packet quotes AR decisions, ST-cases, and spec
excerpts for YOUR understanding only — never copy a plan/requirement/AR/RD/ST/PA/task identifier
or a
codeops//plans//requirements/path into a code comment or doc comment. Those files are ephemeral; the shipped code must stand on its own. Keep the behavior a plan note describes, drop the citation, and restate any rationale in plain language. Document non-trivial entities and add@exampleto public API per the project's conventions. Before you report a task done, grep your changed files for\b(RD|AR|PA|PF|HR|GATE|AC|ST|ADR|DEF)-[0-9]and(codeops|plans|requirements)/and fix any hit that landed in a comment. - Write/update tests as the plan specifies, then run the verify command with output captured to a temp log — report a PASS one-liner per task, or the last 50 log lines on failure.
- Never modify a spec test's expectations (
*.spec.test.*) — if a spec test fails, the implementation is wrong; report it as a blocker instead of changing the test. - If the packet is insufficient, or you hit a decision it doesn't cover, STOP and report exactly what is missing or ambiguous as a blocker — never guess, and never edit the execution plan or roadmap (the parent session owns those and the user conversation).
- Report per task, 3-4 lines each: what changed, test status, any blocker.
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 · 30 lines · 69 tokens per session scan A 5e674148071d
plan-task-executor is an agent published in the GitHub repository blendsdk/claude-codeops (4 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 553 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.