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 --skill task-syncgit 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/skills/obsfx/trekker/task-sync)<a href="https://agentmods.dev/skills/obsfx/trekker/task-sync"><img src="https://agentmods.dev/badge/skills/obsfx/trekker/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/task-sync"><img src="https://agentmods.dev/badge/skills/obsfx/trekker/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.00605 |
| 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 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-sync — 97% identical, 4 lines differ
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? Run trekker task show <id>
2. Make change in Trekker FIRST
3. Mirror to TodoWrite AFTER
4. If they 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.
- yesterday First seen · 95 lines · 23 tokens per session scan A 95f70de31869
task-sync is a skill published in the GitHub repository obsfx/trekker (84 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 605 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 skills, from other repositories
swarm-plan
Full execution protocol for MODE: PLAN -- plan creation, external plan ingestion, QA gate persistence, task granularity, and traceability checks.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
parallel-work-check
Apply before starting work on an existing branch. Checks for parallel work by other agents or developers that may supersede or conflict with your planned changes. Prevents wasted effort on stale branches.
durable-session-state
Persist plans, scope decisions, evidence, and reviewer/critic verdicts to durable files during long or multi-phase tasks so work survives context compaction, session resumes, and handoffs. Use for swarm-mode tasks, before context grows large, when recording approval gates, and when resuming after compaction or a…
issue-ingest
Full execution protocol for MODE: ISSUEINGEST -- GitHub issue intake, localization, spec generation, and transition to the full fix workflow.
phase-wrap
Claude Code adapter for MODE: PHASE-WRAP. Delegates to the canonical opencode-swarm phase boundary protocol.