trekker:list

trekker:list is a command for Claude Code from obsfx/trekker-claude-code. It costs 9 tokens per session (567 once invoked), scanned A, a copy of trekker:list, MIT.

A command for listing Trekker work items, with optional filters and sorting. Trekker is an issue tracker for coding work that keeps task information between sessions.

In plain words
What is it for?
Use it to see active or ready tasks, find high-priority work, review project items, or sort tasks for easier scanning.
Why use it?
It helps you find the right tasks without scanning an unfiltered list, including work by status, priority, type, or recency.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the trekker plugin — 7 skills, 13 commands, 1 agent, 4 hooks shipped together

Good fit Use it to see active or ready tasks, find high-priority work, review project items, or sort tasks for easier scanning.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/obsfx/trekker-claude-code/list
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.

agentmods badge for trekker:list

README.md
[![agentmods](https://agentmods.dev/badge/commands/obsfx/trekker-claude-code/list/github.svg)](https://agentmods.dev/commands/obsfx/trekker-claude-code/list)
Your own site
<a href="https://agentmods.dev/commands/obsfx/trekker-claude-code/list"><img src="https://agentmods.dev/badge/commands/obsfx/trekker-claude-code/list/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.

agentmods 80×15 button for trekker:list

Your own site · 80×15
<a href="https://agentmods.dev/commands/obsfx/trekker-claude-code/list"><img src="https://agentmods.dev/badge/commands/obsfx/trekker-claude-code/list.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 567 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00009 $0.00567
Opus 5.5 $0.00004 $0.00227
Sonnet 5.5 $0.00002 $0.00113
Haiku 4.5 $0.00001 $0.00057

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

Security

Grade A, and why

trekker:list 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:list — 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/list.md · 89 lines

How it starts

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

List and explore tasks with powerful filtering and sorting for situational awareness.

IMPORTANT: /trekker:list is a skill (invoke via Skill tool), NOT a bash command. Use trekker list or trekker task list CLI as shown below.

Two List Commands

  1. trekker list - Unified view across epics, tasks, and subtasks
  2. trekker task list - Tasks only

Common Patterns

Session Start (MANDATORY Context Recovery)

Always gather context via CLI before working:

# 1. SEARCH for what you're working on
trekker search "<topic/area>"

# 2. Review recent activity
trekker history --limit 10

# 3. All active work, prioritized
trekker list --status todo,in_progress --sort priority:asc

# 4. What's currently being worked on?
trekker --toon task list --status in_progress

Finding Work to Do

# Ready tasks by priority
trekker list --type task --status todo --sort priority:asc

# Critical and high priority items
trekker list --priority 0,1 --sort priority:asc

Project Overview

# Everything (all types, all statuses)
trekker list

# Recent items first
trekker list --sort created:desc --limit 20

# Alphabetical for scanning
trekker list --sort title:asc

Filtered Views

# By status
trekker --toon task list --status <status>

# By epic
trekker --toon task list --epic <epic-id>

# By type
trekker list --type task,subtask --status todo

# Combined filters
trekker list --type task --status in_progress --priority 0,1,2

Filter Options

Filter Values
--type task, subtask, epic
--status todo, in_progress, completed, wont_fix, archived
--priority 0 (critical) to 5 (someday)
--sort priority:asc, created:desc, title:asc

Output

Use --toon flag for token-efficient output when listing many tasks.

After Listing

  • If in_progress tasks found: verify you should continue or update status
  • If many todo tasks: consider prioritizing with trekker task update <id> -p <priority>
  • If stale tasks: review and update or archive

Read the full file on GitHub · 89 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. 1mo ago First seen · 89 lines · 9 tokens per session scan A bb1038592178

Subscribe to this mod's changes

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