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/servicegit clone --depth 1 https://github.com/xiaobei930/cc-bestWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/xiaobei930/cc-best/service)<a href="https://agentmods.dev/commands/xiaobei930/cc-best/service"><img src="https://agentmods.dev/badge/commands/xiaobei930/cc-best/service.svg" alt="Measured on agentmods" height="20"></a>What 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.00017 | $0.01091 |
| Opus 5 | $0.00009 | $0.00545 |
| Sonnet 5 | $0.00003 | $0.00218 |
| Haiku 4.5 | $0.00002 | $0.00109 |
Grade A, and why
service 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 3d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/service - 开发服务管理
自动检测项目运行时和包管理器，管理开发服务的启动、停止和重启。支持 6 种语言运行时的自动检测。
使用方式
# 自动检测并启动服务
/cc-best:service
# 停止运行中的服务
/cc-best:service --stop
# 重启服务
/cc-best:service --restart
# 查看服务日志
/cc-best:service --logs
# 指定端口启动
/cc-best:service --port 3000
# 列出检测到的所有服务入口
/cc-best:service --list
运行时自动检测
检测优先级
按以下顺序检测项目运行时：
| 优先级 | 检测文件 | 运行时 | 包管理器 |
|---|---|---|---|
| 1 | package.json |
Node.js | npm/pnpm/yarn/bun |
| 2 | pyproject.toml / requirements.txt |
Python | poetry/pdm/pip |
| 3 | go.mod |
Go | go |
| 4 | Cargo.toml |
Rust | cargo |
| 5 | build.gradle / pom.xml |
Java | gradle/maven |
| 6 | *.csproj / *.sln |
C# | dotnet |
包管理器检测（Node.js）
| 检测文件 | 包管理器 | 启动命令 |
|---|---|---|
bun.lockb |
bun | bun run dev |
pnpm-lock.yaml |
pnpm | pnpm dev |
yarn.lock |
yarn | yarn dev |
package-lock.json |
npm | npm run dev |
启动命令映射
Node.js
# 检查 package.json scripts
# 优先级: dev > start > serve
<PM> run dev # 存在 "dev" script 时
<PM> run start # 存在 "start" script 时
Python
# 检测框架
uvicorn main:app --reload # FastAPI (检测 uvicorn 依赖)
flask run --reload # Flask (检测 flask 依赖)
python manage.py runserver # Django (检测 manage.py)
python -m gunicorn app:app # Gunicorn (生产环境)
Go
# 检测 air 配置
air # 存在 .air.toml 时 (hot reload)
go run . # 默认
go run cmd/server/main.go # 存在 cmd/ 目录时
Rust
cargo watch -x run # 安装了 cargo-watch 时 (hot reload)
cargo run # 默认
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.
- 3d ago First seen · 139 lines · 17 tokens per session scan A a116ed321803
service is a command published in the GitHub repository xiaobei930/cc-best (50 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 1,091 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
validate
You are the quality gate. Your job is to verify that a phase's implementation meets quality standards before the team moves to the next phase. No phase should advance until validation passes.
implement
You are the phase dispatcher. Your job is to route implementation work to the correct phase agent with the right context.
phased-plan
You are generating a 7-phase implementation plan that maps a user story to the structured development workflow.
retro
You are generating a retrospective report for a completed feature. Your job is to analyze git history and project artifacts to surface patterns, measure delivery quality, and suggest workflow improvements.
progress
You are generating a visual progress report showing which phases are complete, in-progress, or pending for the current feature.
commit
You are creating a conventional commit scoped to the current phase of work.