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/mrnine-666/claude-code-quickstart/issue-trackergit clone --depth 1 https://github.com/MrNine-666/claude-code-quickstartWhat 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.01144 |
| Opus 5 | $0.00000 | $0.00572 |
| Sonnet 5 | $0.00000 | $0.00229 |
| Haiku 4.5 | $0.00000 | $0.00114 |
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 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue tracker: GitHub
本仓库的 issue 与 PRD 均以 GitHub issue 保存。所有操作使用 gh CLI。
Conventions
- 创建 issue：
gh issue create --title "..." --body "..."。多行正文使用 heredoc。 - 读取 issue：
gh issue view <number> --comments，使用jq过滤 comment， 并同时获取 label。 - 列出 issue：
gh issue list --state open --json number,title,body,labels,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], comments: [.comments[].body]}]'， 并按需添加--label与--state过滤条件。 - 评论 issue：
gh issue comment <number> --body "..." - 添加或移除 label：
gh issue edit <number> --add-label "..."/--remove-label "..." - 关闭 issue：
gh issue close <number> --comment "..."
仓库身份从 git remote -v 推导；在 clone 中运行时，gh 会自动完成该操作。
Pull Requests as a Triage Surface
是否将 PR 作为需求入口：no。（如果本仓库把外部 PR 当作功能请求，则设为
yes；/triage 会读取此标志。）
设为 yes 时，PR 使用与 issue 相同的 label 和状态，并改用对应的 gh pr 命令：
- 读取 PR：使用
gh pr view <number> --comments，并用gh pr diff <number>查看 diff。 - 列出待 triage 的外部 PR：运行
gh pr list --state open --json number,title,body,labels,author,authorAssociation,comments， 然后只保留authorAssociation为CONTRIBUTOR、FIRST_TIME_CONTRIBUTOR或NONE的记录（排除OWNER/MEMBER/COLLABORATOR）。 - 评论、标记或关闭：使用
gh pr comment、gh pr edit --add-label/--remove-label、gh pr close。
GitHub 的 issue 和 PR 共用编号空间，因此单独的 #42 可能属于任意一种。先运行
gh pr view 42，失败后再回退到 gh issue view 42。
When a Skill Says "Publish to the Issue Tracker"
创建一个 GitHub issue。
When a Skill Says "Fetch the Relevant Ticket"
运行 gh issue view <number> --comments。
Wayfinding Operations
本节供 /wayfinder 使用。map 是单个 issue，child issue 是具体 ticket。
- Map：单个带
wayfinder:maplabel 的 issue，正文保存 Notes / Decisions-so-far / Fog。使用gh issue create --label wayfinder:map创建。 - Child ticket：作为 GitHub sub-issue 链接到 map 的 issue（通过 sub-issues
endpoint 调用
gh api）。如果未启用 sub-issue，则把 child 加入 map 正文的 task list，并在 child 正文开头写入Part of #<map>。Label 使用wayfinder:<type>（research/prototype/grilling/task）。Ticket 被认领后， 分配给负责推进的 developer。 - Blocking：使用 GitHub 原生 issue dependency 作为标准且在 UI 可见的
表达。通过
gh api --method POST repos/<owner>/<repo>/issues/<child>/dependencies/blocked_by -F issue_id=<blocker-db-id>添加依赖边；其中<blocker-db-id>是 blocker 的数字 database id （通过gh api repos/<owner>/<repo>/issues/<n> --jq .id获取，不能使用#number或node_id）。GitHub 的issue_dependencies_summary.blocked_by只报告仍打开的 blocker，并作为实时门禁。无法使用 dependency 时，回退为 child 正文开头的Blocked by: #<n>, #<n>。所有 blocker 关闭后，ticket 才算解除阻塞。 - Frontier query：列出 map 中仍打开的 child（使用
gh issue list --state open， 并限定于 map 的 sub-issue 或 task list），排除存在开放 blocker （issue_dependencies_summary.blocked_by > 0，或Blocked by行中仍有开放 issue）以及已有 assignee 的记录；按 map 顺序选择第一个。 - Claim：
gh issue edit <n> --add-assignee @me，这是 session 的第一次写操作。 - Resolve：先运行
gh issue comment <n> --body "<answer>"，再运行gh issue close <n>，最后向 map 的 Decisions-so-far 追加 context 指针 （gist 和链接）。
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 · 74 lines · 0 tokens per session scan A 58645eabcd14
issue-tracker is an agent published in the GitHub repository MrNine-666/claude-code-quickstart (211 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,144 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.