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/xiaobei930/cc-best/statusgit clone --depth 1 https://github.com/xiaobei930/cc-bestWhat 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.00006 | $0.00744 |
| Opus 5 | $0.00003 | $0.00372 |
| Sonnet 5 | $0.00001 | $0.00149 |
| Haiku 4.5 | $0.00001 | $0.00074 |
Grade A, and why
status 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
/status - 项目状态与诊断
检查项目整体状态，提供健康诊断和改进建议。
参数
| 参数 | 说明 |
|---|---|
| (无参数) | 基本状态检查 |
--full |
完整诊断，包括 CC-Best 组件统计 |
--conflicts |
检测与其他插件的冲突 |
检查项目
执行以下检查并生成状态报告：
1. Git 状态
- 当前分支名称
- 未提交的更改数量
- 与远程的同步状态
- 最近一次提交信息
2. Memory Bank 状态
progress.md行数（超过 300 行提醒归档）- 最后更新时间
- 是否存在未完成任务
3. 依赖状态
- Python 依赖（requirements.txt / pyproject.toml）
- Node.js 依赖（package.json）
- 是否有过期或缺失的依赖
4. 环境配置
- 必要的环境变量是否已设置
.env文件是否存在
5. CC-Best 组件统计（--full）
扫描并统计项目组件：
📊 CC-Best 组件统计
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Commands: 44 个 (commands/*.md)
Skills: 19 个 (skills/*/SKILL.md)
Agents: 8 个 (agents/*.md)
Hooks: 30 个 (scripts/node/hooks/*.js)
Rules: 43 个 (rules/**/*.md)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
6. 插件冲突检测（--conflicts）
检查是否存在与其他插件的潜在冲突：
⚠️ 潜在冲突检测
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
检测到 Superpowers 插件：
- SessionStart hooks 可能冲突
- 建议：CC-Best 用于团队工作流，Superpowers 用于 git 自动化
检测到 code-review 插件：
- 与 code-reviewer agent 功能重叠
- 建议：可共存，agent 做快速检查，插件做深度分析
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
输出格式
📊 项目状态报告
═══════════════════════════════════════
🌿 Git 状态
分支: main
最近提交: abc1234 - feat: add login
工作区: 2 个文件未提交
📝 Memory Bank
progress.md: 150 行 ✅
最后更新: 2026-01-27
📦 依赖
Node.js: ✅ 已安装
Python: ⚠️ 未检测到 requirements.txt
═══════════════════════════════════════
💡 建议:
(如有问题会列出改进建议)
使用场景
- 开始工作前检查项目状态
- 排查问题时快速了解环境
- 确认部署前的准备状态
- 诊断配置问题
- 检测插件冲突（
--conflicts）
记住: Status 是快速诊断工具——30 秒了解项目全貌，比翻阅多个文件高效得多。
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 · 113 lines · 6 tokens per session scan A 610af5a42901
status is a command published in the GitHub repository xiaobei930/cc-best (50 stars, last pushed 2mo ago), licensed MIT. It adds 6 tokens to every session and 744 once invoked, about $0.0000 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
tldr
Re-apply TLDR rules for this turn (verdict first, no filler).
tldr-help
Quick reference card for tldr modes, slash commands, and triggers.
tldr-review
One-line TLDR PR review comments (verdict first, no filler).
guide
Interactive guide to fellowship. Walks you through a real task using the structured research-plan-implement flow, then shows you what's next.
audit-plugin
Audit plugin skills, commands, and agents for structure, size, and naming issues.
lfe-improve-architecture
Find deepening opportunities in the codebase — turn shallow modules into deep ones. Use in Phase 5 (Hygiene sub-pipeline) or when scheduled by session count.