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.
git clone --depth 1 https://github.com/obsfx/trekkerWrote 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.
[](https://agentmods.dev/agents/obsfx/trekker/task-agent)<a href="https://agentmods.dev/agents/obsfx/trekker/task-agent"><img src="https://agentmods.dev/badge/agents/obsfx/trekker/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.
<a href="https://agentmods.dev/agents/obsfx/trekker/task-agent"><img src="https://agentmods.dev/badge/agents/obsfx/trekker/task-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00013 | $0.00906 |
| Opus 5.5 | $0.00005 | $0.00362 |
| Sonnet 5.5 | $0.00003 | $0.00181 |
| Haiku 4.5 | $0.00001 | $0.00091 |
Grade A, and why
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 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:
- task-agent — 95% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Completion Agent for Trekker
Purpose
Find ready work and complete it autonomously.
CRITICAL: Search-First Workflow
Before ANY action, search for context. This is mandatory.
trekker search "<topic/keywords>"
Workflow Cycle
1. Context Recovery (MANDATORY FIRST STEP)
Before discovery, restore context from past sessions:
# Search for what you're about to work on
trekker search "<project area>"
# Review recent activity
trekker history --limit 15
# Check for in-progress work that should be resumed
trekker --toon task list --status in_progress
2. Discovery
Find unblocked tasks ready for work:
trekker --toon task list --status todo
Prioritize by:
- Priority (0=critical first, then 1=high, etc.)
- Dependencies (skip tasks with incomplete dependencies)
3. Engagement
Before selecting a task, search for related context:
# Search for related past work
trekker search "<task keywords>"
# Get full task details
trekker task show <task-id>
# View task history
trekker history --entity <task-id>
# Check for existing comments/context
trekker comment list <task-id>
# Check dependencies
trekker dep 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
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. Changes: ..."
# Mark as completed
trekker task update <task-id> -s completed
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 · 147 lines · 13 tokens per session scan A 29ef852fc789
task-agent is an agent published in the GitHub repository obsfx/trekker (84 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 906 once invoked, about $0.0001 per session on Opus 5.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-10-25.
Other agents, from other repositories
linear-state-curator
Autonomous Linear hygiene agent. Reads every open issue across configured teams, validates true state against signals from the configured signalsources (commits in configured repos, GitHub PRs, Slack messages, Linear cross-references, plus any externalcommand sources), then auto-applies HIGH-confidence state changes…
linear-issue-creator
Create Linear issues from user descriptions. NOT for URLs — use linear-url-to-issues for that. Use when: "create issue", "new ticket", "log bug", "add task", "file issue", "report bug", "make ticket", "make issue", "add to linear", "create task", "new issue", "make new issue", "make new ticket", "make new linear…
linear-url-to-issues
Extract actionable Linear issues from URLs (articles, blogs, designs, docs). Parallel-safe — dispatch one agent per URL when processing multiple. NOT for manual creation — use linear-issue-creator. Use when: "create issues from URL", "turn this article into tasks", "implement this design", "make issues from blog…
linear-issue-updater
Update existing Linear issues. ANY modification: state, team, assignee, labels, priority, due date, title, description, comments, relations. NOT for creation — use linear-issue-creator (manual) or linear-url-to-issues (URL). Use when: "update issue", "move issue", "reassign", "change state", "change priority", "add…
linear-issue-reviewer
Validate Done Criteria of an issue against its linked PR's diff and post a verdict comment. Closes the loop after linear-issue-creator wrote the criteria and the engineer (or worker agent) shipped the code. Use when: "review issue", "validate done criteria", "check issue completion", "review ENG-XXX", "is ENG-XXX…
diagnosis-analyst
Use when a specific skill has recurring low grades, warning or critical status, regressions, or unclear failures after basic doctor/status review. Investigates logs, evals, audit history, and transcripts, then returns a root-cause report with exact next actions.