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 skills add obsfx/trekker-claude-code --skill task-syncgit 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/skills/obsfx/trekker-claude-code/task-sync)<a href="https://agentmods.dev/skills/obsfx/trekker-claude-code/task-sync"><img src="https://agentmods.dev/badge/skills/obsfx/trekker-claude-code/task-sync/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/skills/obsfx/trekker-claude-code/task-sync"><img src="https://agentmods.dev/badge/skills/obsfx/trekker-claude-code/task-sync.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.00023 | $0.00604 |
| Opus 5.5 | $0.00009 | $0.00242 |
| Sonnet 5.5 | $0.00005 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
task-sync 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 today.
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.
This is a copy
97% identical to task-sync — 4 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Synchronization: Trekker is Primary
CRITICAL: Trekker is the PRIMARY task tracker. TodoWrite is secondary.
Trekker persists across sessions in SQLite. TodoWrite only lives within a conversation. When they conflict, Trekker wins.
The Rule
Trekker = Source of Truth (survives context resets)
TodoWrite = Session Mirror (conversation-scoped only)
Automatic Sync Behavior
When Starting a Session
- Read Trekker state first:
trekker --toon list --type task --status todo,in_progress - Populate TodoWrite from Trekker tasks
- Never trust TodoWrite from previous sessions - always refresh from Trekker
When Creating Tasks
1. Create in Trekker FIRST:
trekker task create -t "Title" -d "Description"
2. THEN mirror to TodoWrite:
TaskCreate with same subject
When Updating Tasks
1. Update Trekker FIRST:
trekker task update TREK-n -s in_progress
2. THEN update TodoWrite:
TaskUpdate for corresponding todo
When Completing Tasks
1. Add summary comment to Trekker:
trekker comment add TREK-n -a "claude" -c "Summary: ..."
2. Mark complete in Trekker:
trekker task update TREK-n -s completed
3. Mark complete in TodoWrite:
TaskUpdate status: completed
Priority Order
| Scenario | Action |
|---|---|
| Trekker has task, TodoWrite doesn't | Add to TodoWrite |
| TodoWrite has task, Trekker doesn't | Create in Trekker first |
| Both have task, states differ | Trekker wins, update TodoWrite |
| User creates via TodoWrite | Immediately create in Trekker |
Why Trekker is Primary
- Persistence: Survives context resets, TodoWrite doesn't
- Searchable:
trekker searchfinds past work - Auditable:
trekker historyshows change trail - Dependencies: Trekker tracks task relationships
- Multi-session: Work continues across conversations
Implementation Pattern
Before ANY task operation, think:
1. Is this in Trekker? → trekker task show <id>
2. Make change in Trekker FIRST
3. Mirror to TodoWrite AFTER
4. If conflict → Trekker wins
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.
- today Changed e436b7027c12
- 1mo ago First seen · 95 lines · 23 tokens per session scan A ec203333efca
task-sync is a skill published in the GitHub repository obsfx/trekker-claude-code (4 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 604 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to task-sync, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
flow-next-flow
Use first in a Flow-Next repo for a spec id, change, bug, issue, slow code or metric, cleanup, design fork, dump to explain, repeated mistake, prompt change, what could break, what next. No quick asks.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
flow-next-plan
Plan a feature into a flow-next spec with tasks in .flow/. Use when asked to plan, spec out, or break down work (fn-N ids).
flow-next
Manage .flow/ tasks and specs. Use for show or list tasks, task status, what is ready, show fn-N. NOT for planning or executing (use the plan and work skills).
backlog
Read, work, and maintain a Git repo's deferred-work items in docs/backlog/, one file per item. Use when the user says "backlog", "check backlog", "what's on my backlog", "work the backlog", "address the backlog", "add to backlog", "clean up backlog", or when a review or task produced items that are real but not being…
execute-round
Use when a planned round handoff exists and needs to be implemented end-to-end via the 4-commit chain (entry-admin → BA design → dev body with inline CR + SE → state refresh + self-audit). Dispatches ba-designer / developer / cr-reviewer / se-contract sequentially.