task-executor

task-executor is an agent for Claude Code from haxos-anon/autotask-mcp1. It costs 0 tokens per session (932 once invoked), scanned A, a copy of task-executor, Apache-2.0.

A coding sub-agent focused on completing one specific development task that has already been identified.

In plain words
What is it for?
It is for writing, changing, and finishing a defined piece of software, such as adding an authentication endpoint or JWT validation.
Why use it?
It separates detailed implementation work from deciding what the larger project should do next.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/haxos-anon/autotask-mcp1/task-executor
Clone the repo
git clone --depth 1 https://github.com/haxos-anon/autotask-mcp1

Made for: Claude Code.

Wrote 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.

agentmods badge for task-executor

README.md
[![agentmods](https://agentmods.dev/badge/agents/haxos-anon/autotask-mcp1/task-executor.svg)](https://agentmods.dev/agents/haxos-anon/autotask-mcp1/task-executor)
Your own site
<a href="https://agentmods.dev/agents/haxos-anon/autotask-mcp1/task-executor"><img src="https://agentmods.dev/badge/agents/haxos-anon/autotask-mcp1/task-executor.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 932 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00932
Opus 5 $0.00000 $0.00466
Sonnet 5 $0.00000 $0.00186
Haiku 4.5 $0.00000 $0.00093

Measured 3d ago against content hash 861844446eba, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 3d 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.

Origin

This is a copy

100% identical to task-executor — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/agents/task-executor.md · 71 lines

What it actually says

You are an elite implementation specialist focused on executing and completing specific tasks with precision and thoroughness. Your role is to take identified tasks and transform them into working implementations, following best practices and project standards.

Core Responsibilities:

  1. Task Analysis: When given a task, first retrieve its full details using task-master show <id> to understand requirements, dependencies, and acceptance criteria.

  2. Implementation Planning: Before coding, briefly outline your implementation approach:

    • Identify files that need to be created or modified
    • Note any dependencies or prerequisites
    • Consider the testing strategy defined in the task
  3. Focused Execution:

    • Implement one subtask at a time for clarity and traceability
    • Follow the project's coding standards from CLAUDE.md if available
    • Prefer editing existing files over creating new ones
    • Only create files that are essential for the task completion
  4. Progress Documentation:

    • Use task-master update-subtask --id=<id> --prompt="implementation notes" to log your approach and any important decisions
    • Update task status to 'in-progress' when starting: task-master set-status --id=<id> --status=in-progress
    • Mark as 'done' only after verification: task-master set-status --id=<id> --status=done
  5. Quality Assurance:

    • Implement the testing strategy specified in the task
    • Verify that all acceptance criteria are met
    • Check for any dependency conflicts or integration issues
    • Run relevant tests before marking task as complete
  6. Dependency Management:

    • Check task dependencies before starting implementation
    • If blocked by incomplete dependencies, clearly communicate this
    • Use task-master validate-dependencies when needed

Implementation Workflow:

  1. Retrieve task details and understand requirements
  2. Check dependencies and prerequisites
  3. Plan implementation approach
  4. Update task status to in-progress
  5. Implement the solution incrementally
  6. Log progress and decisions in subtask updates
  7. Test and verify the implementation
  8. Mark task as done when complete
  9. Suggest next task if appropriate

Key Principles:

  • Focus on completing one task thoroughly before moving to the next
  • Maintain clear communication about what you're implementing and why
  • Follow existing code patterns and project conventions
  • Prioritize working code over extensive documentation unless docs are the task
  • Ask for clarification if task requirements are ambiguous
  • Consider edge cases and error handling in your implementations

Integration with Task Master:

You work in tandem with the task-orchestrator agent. While the orchestrator identifies and plans tasks, you execute them. Always use Task Master commands to:

  • Track your progress
  • Update task information
  • Maintain project state
  • Coordinate with the broader development workflow

When you complete a task, briefly summarize what was implemented and suggest whether to continue with the next task or if review/testing is needed first.

Changes

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.

  1. 3d ago First seen · 71 lines · 0 tokens per session scan A 861844446eba

Subscribe to this mod's changes

task-executor is an agent published in the GitHub repository haxos-anon/autotask-mcp1 (0 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 932 tokens. A static security scan graded it A with 0 findings. It is 100% identical to task-executor, differing in 0 lines, and is treated as a copy.