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 commands/linfee/spec-kit-cn/taskstoissuesgit clone --depth 1 https://github.com/Linfee/spec-kit-cnWhat 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.00032 | $0.00335 |
| Opus 5 | $0.00016 | $0.00168 |
| Sonnet 5 | $0.00006 | $0.00067 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
taskstoissues 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.
What it actually says
用户输入
$ARGUMENTS
你必须在继续之前考虑用户输入（如果非空）.
大纲
- 从仓库根目录运行
{SCRIPT}并解析 FEATURE_DIR 和 AVAILABLE_DOCS 列表. 所有路径必须是绝对路径. 对于参数中的单引号如 "I'm Groot", 使用转义语法: 例如 'I'''m Groot'（或尽可能使用双引号: "I'm Groot"）. - 从执行的脚本中, 提取 任务 的路径.
- 通过运行以下命令获取 Git 远程仓库:
git config --get remote.origin.url
[!CAUTION] 仅当远程仓库是 GITHUB URL 时才继续下一步
- 对于列表中的每个任务, 使用 GitHub MCP 服务器在与 Git 远程仓库对应的仓库中创建一个新议题.
[!CAUTION] 在任何情况下都不要在与远程 URL 不匹配的仓库中创建议题
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 · 34 lines · 32 tokens per session scan A 25f58b49165f
taskstoissues is a command published in the GitHub repository Linfee/spec-kit-cn (695 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 335 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-30.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
project-recap
Generate a visual project recap for context switching.
ado-pull
Pull latest changes from Azure DevOps (like git pull). Supports increment, project, or full living docs sync.
issue-amend
Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.
dispatch-worker
Run one in-session-agent Worker tick (RFC-0041 §4.3.1).
guide
You are a triage agent who continuously prioritizes loom:issue issues by applying loom:urgent to the top 3 priorities.