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.
git 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/plugins/obsfx/trekker/claude-code)<a href="https://agentmods.dev/plugins/obsfx/trekker/claude-code"><img src="https://agentmods.dev/badge/plugins/obsfx/trekker/claude-code/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/plugins/obsfx/trekker/claude-code"><img src="https://agentmods.dev/badge/plugins/obsfx/trekker/claude-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
trekker 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.
What it actually says
{
"name": "trekker",
"description": "AI-optimized issue tracker for coding workflows. Search-first workflow with persistent task memory across sessions, driven through the trekker CLI.",
"version": "1.12.0",
"author": {
"name": "Omercan Balandi",
"url": "https://github.com/obsfx"
},
"repository": "https://github.com/obsfx/trekker",
"license": "MIT",
"homepage": "https://github.com/obsfx/trekker/tree/main/plugins/claude-code",
"keywords": [
"issue-tracker",
"task-management",
"ai-workflow",
"agent-memory",
"search-first",
"context-recovery",
"cli"
]
}
What it installs
The manifest is a name and a version. 7 skills, 13 commands, 1 agent, 3 hooks travel with it, and installing the plugin installs all of them — 283 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill trekker A 11 tokens
- Skill planning A 16 tokens
- Skill issue-tracking A 34 tokens
- Skill search A 14 tokens
- Skill task-sync A 23 tokens
- Skill find-duplicates A 21 tokens
- Skill smart-query A 10 tokens
- Command trekker:history A 17 tokens
- Command trekker:list A 9 tokens
- Command trekker:task-agent A 16 tokens
- Command trekker:start A 9 tokens
- Command trekker:create A 10 tokens
- Command trekker:blocked A 10 tokens
- Command trekker:comment A 11 tokens
- Command trekker:epic A 9 tokens
- Command trekker:show A 11 tokens
- Command trekker:ready A 11 tokens
- Command trekker:done A 10 tokens
- Command trekker:prime A 10 tokens
- Command trekker:deps A 8 tokens
- Agent task-agent A 13 tokens
- Hook TaskCompleted A not measured
- Hook SessionStart A not measured
- Hook PreCompact A not measured
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 · 22 lines scan A 0d76ad366e67
trekker is a plugin published in the GitHub repository obsfx/trekker (84 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
beads-superpowers
Superpowers skills + Beads issue tracking for Claude Code, Codex, OpenCode, and 7 more AI coding agents. Composable skills + persistent task memory.
beads-superpowers
Superpowers skills + Beads issue tracking for Gemini CLI. Composable skills + persistent task memory.
linear-workspace
Linear issue management for Claude Code — search, bulk operations, intelligent agents, config-driven curator. Backed by the elnora-linear CLI.
storybloq
Project memory for Claude Code and Codex. Storybloq stores tickets, issues, handovers, and lessons in a .story/ folder inside your repo.
ccthread
Read, search, and summarize Claude Code conversation logs from /.claude/projects.
trelly
Trello CLI + MCP tools — boards, lists, cards, search, and raw API via trelly-mcp.