What is trekker:task-agent?

An autonomous task agent that finds ready work in a Trekker task list and completes it. It follows task priorities and dependencies while recording progress.

Use it to select unblocked tasks, mark them in progress, implement focused changes, and document progress until it reaches a blocker or runs out of ready work.

It reduces the need to repeatedly inspect task lists, start work, and update statuses manually. It stops when the ready work is finished or when user input or an external fix is needed.

trekker:task-agent — Command for Claude Code by obsfx

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.

Clone the repo

git clone --depth 1 https://github.com/obsfx/trekker-claude-code

Made for: Claude Code.

Or install trekker, the plugin that ships this one along with the rest of its 7 skills, 13 commands, 1 agent, 4 hooks.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/obsfx/trekker-claude-code/task-agent/github.svg)](https://agentmods.dev/commands/obsfx/trekker-claude-code/task-agent)

Your own site

<a href="https://agentmods.dev/commands/obsfx/trekker-claude-code/task-agent"><img src="https://agentmods.dev/badge/commands/obsfx/trekker-claude-code/task-agent/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/obsfx/trekker-claude-code/task-agent"><img src="https://agentmods.dev/badge/commands/obsfx/trekker-claude-code/task-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 623 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 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.

Model	Per session	Once invoked
Fable 5.1	$0.00016	$0.00623
Opus 5.5	$0.00006	$0.00249
Sonnet 5.5	$0.00003	$0.00125
Haiku 4.5	$0.00002	$0.00062

Measured 1mo ago against content hash 227b20f52a18, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

trekker:task-agent 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 1mo 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 trekker:task-agent — 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.

commands/task-agent.md · 107 lines

How it starts

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

Run as an autonomous task agent that finds ready work and completes it without user intervention.

IMPORTANT: /trekker:task-agent is a skill (invoke via Skill tool), NOT a bash command.

Mode

This is an autonomous workflow. Once started, work through tasks until:

All ready tasks are completed
A task requires user input/decision
An external blocker is encountered

Workflow Cycle

1. Discovery

Find unblocked tasks ready for work:

# Check for in-progress work first (resume if exists)
trekker --toon task list --status in_progress

# Find ready tasks by priority
trekker --toon task list --status todo

Prioritize by:

Priority (0=critical first, then 1=high, etc.)
Skip tasks with incomplete dependencies

2. Engagement

Select a task and prepare:

# Get full task details
trekker task show <task-id>

# Check for existing comments/context
trekker comment list <task-id>

# Mark as in progress
trekker task update <task-id> -s in_progress

3. Execution

Complete the work according to the task description:

Follow project coding standards
Make minimal, focused changes
Document significant decisions

4. Documentation

Track discoveries and related work:

# Create tasks for discovered bugs or improvements
trekker task create -t "New issue title" -d "description"

# Link dependencies if needed
trekker dep add <new-task-id> <original-task-id>

# Add progress comments for complex work
trekker comment add <task-id> -a "claude" -c "Progress: ..."

5. Closure

Complete the task properly:

# Add summary comment (required before completion)
trekker comment add <task-id> -a "claude" -c "Summary: implemented X in files A, B"

# Mark as completed
trekker task update <task-id> -s completed

6. Iteration

Return to Discovery phase for the next task.

Rules

Always set status to in_progress before starting work
Always add a summary comment before marking complete
Create new tasks for discovered bugs - don't scope creep
Stop and ask user if:
- Task requirements are unclear
- Multiple valid approaches exist
- External action is needed (e.g., API keys, permissions)
Mark tasks wont_fix if blocked by external factors

Read the full file on GitHub · 107 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.

1mo ago First seen · 107 lines · 16 tokens per session scan A 227b20f52a18

Subscribe to this mod's changes

trekker:task-agent is a command published in the GitHub repository obsfx/trekker-claude-code (4 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 623 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to trekker:task-agent, differing in 0 lines, and is treated as a copy.

Building agents Claude Code Project management ai ai-agents claude issue-tracker plugin

flow

Conductor - an idea or change request, a spec or task id, a tracker issue, a branch or path, a bug report, a how or why question, something slow, a behaviour-keeping cleanup, a design fork, or "what next"; --auto drives a ready spec unattended (--tick for one hop) and ends with a PILOTVERDICT line; --until=merge…

gmickel/flow-next · 86 tokens

trekker:task-agent