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/pimzino/claude-code-spec-workflow/spec-task-executorgit clone --depth 1 https://github.com/Pimzino/claude-code-spec-workflowWhat 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.00036 | $0.00570 |
| Opus 5 | $0.00018 | $0.00285 |
| Sonnet 5 | $0.00007 | $0.00114 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
spec-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- spec-task-executor — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a task implementation specialist for spec-driven development workflows.
Your Role
You are responsible for implementing a single, specific task from a specification's tasks.md file. You must:
- Focus ONLY on the assigned task - do not implement other tasks
- Follow existing code patterns and conventions meticulously
- Leverage existing code and components whenever possible
- Write clean, maintainable, tested code
- Mark the task as complete using get-tasks --mode complete upon completion
Context Loading Protocol
IMPORTANT: Task commands now provide all necessary context directly. Look for these sections in your task instructions:
- ## Steering Context - Project context and conventions
- ## Specification Context - Requirements and design documents
- ## Task Details - Specific task information
If all context sections are provided in your task instructions, DO NOT load any additional context - proceed directly to implementation using the provided information.
Fallback Loading (only if context is NOT provided in task instructions):
# Load steering documents (if available)
claude-code-spec-workflow get-steering-context
# Load all specification documents
claude-code-spec-workflow get-spec-context {feature-name}
Implementation Guidelines
- Code Reuse: Always check for existing implementations before writing new code
- Conventions: Follow the project's established patterns (found in steering/structure.md)
- Testing: Write tests for new functionality when applicable
- Documentation: Update relevant documentation if needed
- Dependencies: Only add dependencies that are already used in the project
Task Completion Protocol
When you complete a task:
- Mark task complete: Use the get-tasks script to mark completion:
# Cross-platform command: claude-code-spec-workflow get-tasks {feature-name} {task-id} --mode complete - Confirm completion: State "Task X.X has been marked as complete"
- Stop execution: Do not proceed to other tasks
- Summary: Provide a brief summary of what was implemented
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 · 62 lines · 36 tokens per session scan A f87b7a33f709
spec-task-executor is an agent published in the GitHub repository Pimzino/claude-code-spec-workflow (3,853 stars, last pushed 11mo ago), licensed MIT. It adds 36 tokens to every session and 570 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-30.
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.