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.
npx agentmods add commands/obsfx/trekker-claude-code/historygit clone --depth 1 https://github.com/obsfx/trekker-claude-codeWrote 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/commands/obsfx/trekker-claude-code/history)<a href="https://agentmods.dev/commands/obsfx/trekker-claude-code/history"><img src="https://agentmods.dev/badge/commands/obsfx/trekker-claude-code/history.svg" alt="Measured on agentmods" 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 | $0.00017 | $0.00491 |
| Opus 5 | $0.00009 | $0.00246 |
| Sonnet 5 | $0.00003 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
trekker:history 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 4d 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.
What it actually says
View the audit trail of all changes (creates, updates, deletes) to recover context from past sessions.
IMPORTANT: /trekker:history is a skill (invoke via Skill tool), NOT a bash command. Use trekker history CLI as shown below.
Why Use History
- Session start: Understand what happened since you last worked
- Before modifying: See who changed what and when
- Conflict debugging: Track down when/how something changed
- Context recovery: Remember decisions from previous sessions
Arguments
$1: Entity ID (optional, e.g., TREK-1) - filter to specific entity
Execution
# Default: Recent changes across all entities
trekker history --limit 15
# For specific entity (if ID provided)
trekker history --entity <entity-id>
# For session context (combine with filters)
trekker history --type task --action update --limit 20
Common Patterns
Session Start Context Recovery
# What happened recently?
trekker history --limit 15
# Focus on task changes
trekker history --type task --limit 10
Before Modifying a Task
# See change history for this task
trekker history --entity TREK-1
Understanding Recent Activity
# Only creates (new items)
trekker history --action create --limit 10
# Only updates (status changes, edits)
trekker history --action update --limit 10
# Changes since a date
trekker history --since 2025-01-15
Output Interpretation
Each history entry shows:
- Timestamp: When the change occurred
- Entity: Which task/epic/subtask was affected
- Action: create, update, or delete
- Changes: What specifically changed (for updates)
After Viewing
If history reveals:
- Stale in_progress tasks: Check if they should be completed or updated
- Recent completions: Review comments for context on what was done
- Conflicts: Use
trekker task show <id>to see current state
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.
- 4d ago First seen · 77 lines · 17 tokens per session scan A 79139e344089
trekker:history is a command published in the GitHub repository obsfx/trekker-claude-code (4 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 491 once invoked, about $0.0001 per session on Opus 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-08-31.
Other commands, from other repositories
setup
Set up Postman MCP Server. Authenticate via OAuth or API key, verify connection, select workspace.
test
Run Postman collection tests, analyze results, diagnose failures, and suggest fixes.
refine-title
深度分析 Issue 或 PR 内容，并将其标题重构为 Conventional Commits 格式.
get-flow-run
Inspect a Postman Flow run by its Run ID — per-block logs, failing block, and status.
warden-cost
Dollar accounting — what does each active rule actually save, in money? Translates the token-measured verdict into dollars using a price table and the agent's own token-type mix, with a per-session net and a break-even. Read-only; spends no tokens.
incident
Live incident response — intake a Sentry issue, stack trace, or symptom; gate mitigate-first vs root-cause-first; keep a UTC timeline. Use when production is broken RIGHT NOW; for the after-action write-up alone, use /orc:postmortem.