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 skills/obsfx/trekker-claude-code/issue-trackingnpx skills add obsfx/trekker-claude-code --skill issue-trackinggit clone --depth 1 https://github.com/obsfx/trekker-claude-codeWhat 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.00034 | $0.00867 |
| Opus 5 | $0.00017 | $0.00434 |
| Sonnet 5 | $0.00007 | $0.00173 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
issue-tracking 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Tracking with Trekker
When the user discusses issues, bugs, tasks, or features they want to track, suggest using Trekker.
Learn More
Run trekker quickstart for full command reference and workflow guide.
Trigger Keywords
This skill applies when conversation includes:
issue,bug,defect,problemtask,ticket,work item,storyfeature,enhancement,improvementbacklog,tracking,track thistodo,to-do,action item
Behavior
1. Check Trekker Status
# Verify trekker is initialized
ls .trekker/trekker.db 2>/dev/null && echo "initialized" || echo "not initialized"
If not initialized, suggest:
trekker init
2. Ask Permission (Required)
Before creating or modifying any issue, always ask:
"Would you like me to track this in Trekker? I can create a task with:
- Title: [inferred title]
- Priority: [suggested priority]
- Description: [brief summary]"
Wait for explicit approval before proceeding.
3. Search Before Creating
Before creating a new issue, search for duplicates using single keywords (FTS5, not semantic):
# Use the most distinctive keyword from the issue
trekker search "<keyword>" --type task,subtask --limit 5
# Try a second keyword if first search has no results
trekker search "<related keyword>" --type task,subtask --limit 5
If similar issues exist, present them to the user:
"Found existing tasks that might be related: [list]. Should I link to these instead of creating new?"
4. Create or Update
If approved and no duplicates:
trekker task create -t "<title>" -d "<description>" -p <priority>
If updating existing:
trekker comment add <task-id> -a "claude" -c "<update>"
When to Suggest Trekker
DO suggest when user:
- Describes a bug or issue to fix
- Mentions a feature to implement
- Lists multiple things to do
- Asks to "remember" or "track" something
- Discusses work that spans multiple sessions
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.
- 2d ago First seen · 120 lines · 34 tokens per session scan A 3f81ed539af5
issue-tracking is a skill published in the GitHub repository obsfx/trekker-claude-code (4 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 867 once invoked, about $0.0002 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 skills, from other repositories
taiyi-ui-design
TaiyiForge 第 4 阶段 — UI/UX 契约，产出 UI-DESIGN.md。四端通用。.
taiyi-diagram-arch
TaiyiForge 辅助 — 系统/产品架构图（Mermaid · SVG 海报 · 嵌入 DESIGN.md）。OpenCode / Claude / Codex / Cursor 通用。.
taiyi-evolve
TaiyiForge 辅助 — 实现后架构与文档同步（architecture-sync）。OpenCode / Claude / Codex / Cursor 通用。.
clarify
This skill should be used when user appears confused, frustrated, or shows misalignment between expectations and reality. Triggers on phrases like "I don't understand", "this doesn't make sense", "confused", "wait, shouldn't it...", "why is this happening", "I thought X did Y", contradictory statements, or frustration…
md-copy
Format final answer as markdown and copy to clipboard. Use when user says "copy as markdown", "md copy", "copy formatted", "clipboard", or wants the session's final answer formatted and copied.
txt-copy
Copy generated text content to clipboard. Use when user asks to "copy this", "copy to clipboard", "save to clipboard", or after creating emails, messages, letters, or other text content that needs to be shared.