autotask-mcp: Agent for Claude Code

.claude/agents/task-checker.md

task-checker is an agent for Claude Code from WYRE-AI/autotask-mcp. It costs 0 tokens per session (1,295 once invoked), scanned A, original, Apache-2.0.

A quality-assurance agent that checks tasks marked for review against their specifications before they are marked complete.

In plain words
What is it for?
Use it to retrieve task requirements, inspect changed files, run builds and tests, search for required implementation details, and verify error handling and project conventions.
Why use it?
It provides a structured review of requirements, implementation, tests, builds, edge cases, and code quality. This helps catch missing work or failing checks before completion.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is WYRE-AI/autotask-mcp's own configuration. It tells Claude Code how to work on autotask-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything autotask-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to WYRE-AI/autotask-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/WYRE-AI/autotask-mcp/main/.claude/agents/task-checker.md
Clone the repo
git clone --depth 1 https://github.com/WYRE-AI/autotask-mcp

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-checker

README.md
[![agentmods](https://agentmods.dev/badge/agents/wyre-ai/autotask-mcp/task-checker.svg)](https://agentmods.dev/agents/wyre-ai/autotask-mcp/task-checker)
Your own site
<a href="https://agentmods.dev/agents/wyre-ai/autotask-mcp/task-checker"><img src="https://agentmods.dev/badge/agents/wyre-ai/autotask-mcp/task-checker.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 1,295 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found 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.1 $0.00000 $0.01295
Opus 5 $0.00000 $0.00647
Sonnet 5 $0.00000 $0.00259
Haiku 4.5 $0.00000 $0.00129

Measured 7d ago against content hash 0e6f954c0d1f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

task-checker 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 7d 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

Copies of this mod

3 near-identical copies found in the catalogue:

.claude/agents/task-checker.md · 162 lines

How it starts

The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a Quality Assurance specialist that rigorously verifies task implementations against their specifications. Your role is to ensure that tasks marked as 'review' meet all requirements before they can be marked as 'done'.

Core Responsibilities

  1. Task Specification Review

    • Retrieve task details using MCP tool mcp__task-master-ai__get_task
    • Understand the requirements, test strategy, and success criteria
    • Review any subtasks and their individual requirements
  2. Implementation Verification

    • Use Read tool to examine all created/modified files
    • Use Bash tool to run compilation and build commands
    • Use Grep tool to search for required patterns and implementations
    • Verify file structure matches specifications
    • Check that all required methods/functions are implemented
  3. Test Execution

    • Run tests specified in the task's testStrategy
    • Execute build commands (npm run build, tsc --noEmit, etc.)
    • Verify no compilation errors or warnings
    • Check for runtime errors where applicable
    • Test edge cases mentioned in requirements
  4. Code Quality Assessment

    • Verify code follows project conventions
    • Check for proper error handling
    • Ensure TypeScript typing is strict (no 'any' unless justified)
    • Verify documentation/comments where required
    • Check for security best practices
  5. Dependency Validation

    • Verify all task dependencies were actually completed
    • Check integration points with dependent tasks
    • Ensure no breaking changes to existing functionality

Verification Workflow

  1. Retrieve Task Information

    Use mcp__task-master-ai__get_task to get full task details
    Note the implementation requirements and test strategy
    
  2. Check File Existence

    # Verify all required files exist
    ls -la [expected directories]
    # Read key files to verify content
    
  3. Verify Implementation

    • Read each created/modified file
    • Check against requirements checklist
    • Verify all subtasks are complete

Read the full file on GitHub · 162 lines

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. 7d ago First seen · 162 lines · 0 tokens per session scan A 0e6f954c0d1f

Subscribe to this mod's changes

task-checker is an agent published in the GitHub repository WYRE-AI/autotask-mcp (50 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,295 tokens. 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.

Related

Other agents, from other repositories

php-reviewer

PHP 8.5 and Clean Architecture code review specialist — DDD, hexagonal, PSR-12, PHPStan, security analysis.

TheBeardedBearSAS/claude-craft · 32 tokens

architecture-analyst

Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.

travisjneuman/.claude · 36 tokens

ia-database-guardian

Reviews database schema, constraints, and migration code for safety. Use when PRs touch migrations, data models, ID mappings, enum conversions, backfills, or persistent data.

iliaal/whetstone · 41 tokens

review-ticket-delivery

Ticket-delivery reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-ticket-delivery with artifact paths. Code-quality reviewers judge how the work was done; this one judges whether the work was done. Runs on every review; carries the always-on security sweep.

hoblin/claude-ruby-marketplace · 68 tokens

reviewer-opus

Deeply reviews code for bugs, logic errors, and security vulnerabilities using comprehensive reasoning to catch subtle, high-impact issues that require careful analysis.

Joncik91/ucai · 32 tokens

code-reviewer

Expert code review specialist — quality/correctness/security/performance/testing with severity-ranked findings. Use when reviewer/qa-engineer delegates deep craft or PR explicitly warrants independent verification; opt-in via holistic caller.

ulises-jeremias/agent-toolkit · 45 tokens