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/peterfei/ai-agent-team/threadgit clone --depth 1 https://github.com/peterfei/ai-agent-teamWhat 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.00016 | $0.01445 |
| Opus 5 | $0.00008 | $0.00723 |
| Sonnet 5 | $0.00003 | $0.00289 |
| Haiku 4.5 | $0.00002 | $0.00145 |
Grade A, and why
thread 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Thread Manager Command
This command allows you to manage conversation threads using the thread-manager MCP server.
Usage
/thread new "Title" [options]: Create a new thread/thread switch <id>: Switch to a specific thread/thread update [options]: Update current thread metadata/thread delete <id>: Delete a thread/thread show [id]: Show thread details/threador/thread info: Show current thread info
Subcommands
New Thread
Create a new thread and optionally switch to it.
/thread new "Implement User Auth" --tags backend,auth
Options:
--desc "Description": Add a description--tags tag1,tag2: Add tags (comma separated)--no-switch: Do not switch to the new thread immediately
Switch Thread
Switch context to another thread.
/thread switch <thread-id>
/thread <thread-id>
Update Thread
Update the metadata of the current or specified thread.
/thread update --title "New Title" --add-tags tag3
Delete Thread
Delete a thread permanently.
/thread delete <thread-id> --confirm
Show/Info
Show details about a thread.
/thread show <thread-id>
/thread info # Shows current thread
Implementation Details for Claude
⚠️ 前置检查（最高优先级）
在执行任何操作之前，必须先检查 thread-manager MCP 服务器是否可用。
判断方法：检查当前可用的工具列表中是否包含 mcp__thread-manager__* 系列工具（如 mcp__thread-manager__list_threads、mcp__thread-manager__switch_thread 等）。
如果 MCP 工具不可用，必须立即输出以下错误信息并停止，不要尝试调用任何工具：
❌ thread-manager MCP 服务器未配置
当前项目未配置 thread-manager MCP 服务器，无法使用线程管理功能。
🔧 解决方案：
方案 1：全局安装（推荐，一次配置全局可用）
claude mcp add thread-manager -s user -- node <path-to-thread-manager>/dist/index.js
方案 2：项目级安装
claude mcp add thread-manager -s project -- node <path-to-thread-manager>/dist/index.js
方案 3：切换到已配置该服务的项目目录
添加后需要重启 Claude Code 会话才能生效。
🔴 重要：绝对不要在 MCP 不可用时尝试调用工具，这会导致命令卡住无响应！
正常流程
当用户调用此命令时，您应该：
- 检查 MCP 可用性：确认
mcp__thread-manager__*工具存在。如不存在，输出上述错误信息并停止。 - 解析子命令：识别它是
new、switch、update、delete、show还是 ID（这意味着切换）。 - 调用相应的 MCP 工具：
new->thread-manager.create_threadswitch或<id>->thread-manager.switch_threadlist->thread-manager.list_threadsupdate->thread-manager.update_threaddelete->thread-manager.delete_threadshow或info->thread-manager.get_thread或thread-manager.get_current_thread
- 格式化输出：将结果美观地呈现给用户。
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 · 189 lines · 16 tokens per session scan A 74068be8d7b5
thread is a command published in the GitHub repository peterfei/ai-agent-team (428 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 1,445 once invoked, about $0.0001 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
better-auth:add-plugin
Add a better-auth plugin to an existing project. Configures server and client plugins with proper imports.
skill-inbox
Unified entry point for managing skill suggestions and browsing all installed skills. Provides two views: suggestions (default) and all skills.
cti-status
Health check — backend tier, case store, MCP tools, API credit balances. Run this when something behaves oddly. Usage: /cti-status.
send
Send a message to a peer session.
reskin
Extract a measured design signature (type ramp, accent + its budget, grid unit, radius, layout) from a reference image or site, write it to signature.json, and drive the build to match it — "steal this vibe" as a spec, not pixels.
enum-udp
UDP scan + service follow-up — top ports first, full sweep only when justified.