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 agents/xaviw/skills-manager/issue-trackergit clone --depth 1 https://github.com/Xaviw/skills-managerWrote 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/agents/xaviw/skills-manager/issue-tracker)<a href="https://agentmods.dev/agents/xaviw/skills-manager/issue-tracker"><img src="https://agentmods.dev/badge/agents/xaviw/skills-manager/issue-tracker.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.00000 | $0.00424 |
| Opus 5 | $0.00000 | $0.00212 |
| Sonnet 5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
issue-tracker 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 3d 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
Issue tracker：本地 Markdown
本仓库的 issue 和 spec（也称 PRD）使用 .scratch/ 下的 Markdown 文件管理。
约定
- 每个 feature 使用一个目录：
.scratch/<feature-slug>/ - Spec 路径为
.scratch/<feature-slug>/spec.md - 每个实现 ticket 使用独立文件：
.scratch/<feature-slug>/issues/<NN>-<slug>.md - Ticket 从
01开始编号，不使用合并的 tickets 文件 - 评论和讨论记录追加到文件底部的
## Comments标题下
当 skill 要求“发布到 issue tracker”时
在 .scratch/<feature-slug>/ 下创建文件；目录不存在时一并创建。
当 skill 要求“获取相关 ticket”时
读取用户提供的文件路径或 issue 编号对应的文件。
Wayfinding 操作
/wayfinder 使用一个 map 文件，并为每个 ticket 创建一个子文件。
- Map：
.scratch/<effort>/map.md，包含 Notes、Decisions-so-far 和 Fog - 子 ticket：
.scratch/<effort>/issues/NN-<slug>.md，从01开始编号 - 类型：使用
Type:记录research、prototype、grilling或task - 状态：使用
Status:记录claimed或resolved - 阻塞关系：在文件顶部附近使用
Blocked by: NN, NN - Frontier：扫描未关闭、未阻塞且未认领的 ticket，编号最小者优先
- 认领：开始工作前将
Status:改为claimed并保存 - 解决：在
## Answer下追加答案，将状态改为resolved，再把摘要和链接追加到map.md的 Decisions-so-far
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.
- 3d ago First seen · 33 lines · 0 tokens per session scan A ed646aca4768
issue-tracker is an agent published in the GitHub repository Xaviw/skills-manager (5 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 424 tokens. 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 agents, from other repositories
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
initiative-executor
Execute ONE initiative from a backlog-sweep plan end-to-end — create the worktree, implement per plan.md, validate, open the PR, return a >> envelope. Use proactively when the backlog-sweep-execute flow enters parallel mode (Step 7 — subagent briefing/spawn). Orchestrator supplies initiative id, plan path, and tool…
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
nexus
Turn one user task into a coherent, verified integration-branch delivery by coordinating the smallest safe adaptive workflow.