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/1072636071/win-shell-mcp/issue-trackergit clone --depth 1 https://github.com/1072636071/win-shell-mcpWhat 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.00568 |
| Opus 5 | $0.00000 | $0.00284 |
| Sonnet 5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
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 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
Issue 跟踪器：本地 Markdown
此仓库的 issue 和 PRD 以 markdown 文件形式存放在 .scratch/ 中。
约定
- 每个功能一个目录：
.scratch/<NN>-<feature-slug>/，<NN>为从01起的全局递增顺序号，按创建先后排列（如01-login、02-checkout） - PRD 是
.scratch/<NN>-<feature-slug>/PRD.md - 实现 issue 是
.scratch/<NN>-<feature-slug>/issues/<NN>-<slug>.md，从01编号 - Triage 状态记录为每个 issue 文件顶部附近的
Status:行（角色字符串见triage-labels.md） - 评论和对话历史追加到文件底部，在
## 评论标题下
当技能说"发布到 issue tracker"时
在 .scratch/<NN>-<feature-slug>/ 下创建新文件（如需要则创建目录；目录名带从 01 起的全局递增顺序号）。
当技能说"获取相关工单"时
读取引用路径的文件。用户通常会直接传递路径或 issue 编号。
Wayfinding 操作
由 /jxx-wayfinder 使用。地图是一个文件，每个工单有一个子文件。
- 地图：
.scratch/<NN>-<effort>/map.md— 笔记/已做决策/迷雾正文。 - 子工单：
.scratch/<NN>-<effort>/issues/NN-<slug>.md，从01编号，问题在正文中。Type:行记录工单类型（research/prototype/grilling/task）；Status:行记录claimed/resolved。 - 阻塞：顶部附近的
Blocked by: NN, NN行。当其列出的所有文件都resolved时，工单解除阻塞。 - 前沿：扫描
.scratch/<NN>-<effort>/issues/中开放、未阻塞、未认领的文件；按编号优先，第一个胜出。 - 认领：设置
Status: claimed并在任何工作前保存。 - 解决：在
## 答案标题下追加答案，设置Status: resolved，然后将上下文指针（gist + 链接）追加到map.md中地图的已做决策中。
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 · 30 lines · 0 tokens per session scan A 104de2b1ec21
issue-tracker is an agent published in the GitHub repository 1072636071/win-shell-mcp (0 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 568 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.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
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.
dependency-blocker-monitor
Use when monitoring workcell BOM dependencies and cell health to open or resolve blocker issues when a cell fails or recovers. USE FOR: read workcell BOM dependencies, monitor cell deployment status, create blocker issues, and resolve them on recovery. DO NOT USE FOR: general incident response, application code, or…
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.