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 skills/zzusp/doc-first-dev/spec-multinpx skills add zzusp/doc-first-dev --skill spec-multigit clone --depth 1 https://github.com/zzusp/doc-first-devWhat 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.00559 |
| Opus 5 | $0.00000 | $0.00280 |
| Sonnet 5 | $0.00000 | $0.00112 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
spec-multi 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
spec-multi — 多服务并行开发
处理跨多个服务/项目的需求开发。单服务日常迭代用 /spec-first；跨服务协调用本 skill。
触发条件
用户描述的需求涉及多个服务同时变更（如前端+后端、后端+Python服务、全栈+微服务等）。
前置检查
检查 docs/plans/SERVICES.md 是否存在（相对于 workspace root）：
- 不存在 → 读取 init.md，完成服务注册后返回本流程
- 存在 → 展示服务清单摘要（服务名、路径、端口），继续
流程
Step0（需求接收）→ Phase A（分析）→ Phase B（开发）→ Phase C（集成验收）→ Phase D（收尾）
用户指定从某个 Phase 开始时，从该 Phase 直接切入（如"从 Phase B 继续"）。
异常处理规则见 error-handling.md。
各阶段入口
| 阶段 | 文件 | 核心产出 |
|---|---|---|
| Step 0 | step0.md | 创建或定位需求文档 |
| Phase A | phase-a.md | 链路追踪 + 需求文档填充 + 确认门 |
| Phase B | phase-b.md | 按依赖顺序编排各服务代码实现 |
| Phase C | phase-c.md | 启动所有服务 + 单服务验收 + E2E 验收 |
| Phase D | phase-d.md | 一致性审计 + 交付摘要 |
关键约定
需求文档：docs/plans/requirements/<需求名>.md（workspace root 下）
T-xxx 格式：T-<序号> · [<服务名>] · P0/P1/P2 · 状态 — 描述（file:method）
A-xxx 格式：A-<序号> · [<服务名>|E2E] · <接口/场景> · 状态 — 可执行断言
[E2E]表示跨服务集成验收- 序号全文档内唯一递增（不区分服务）
- Phase B 通过过滤
[服务名]标签分配 subagent 任务
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/multi-spec-blank.md 1.3 KB
- assets/services-index-blank.md 559 B
- error-handling.md 1.6 KB
- evals/eval-01-cross-service-feature.md 2.5 KB
- evals/eval-02-interface-drift.md 1.8 KB
- evals/eval-03-partial-service-change.md 2.2 KB
- init.md 1.9 KB
- phase-a.md 4.3 KB
- phase-b.md 2.6 KB
- phase-c.md 6.1 KB
- phase-d.md 2.9 KB
- step0.md 1.2 KB
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 · 47 lines · 0 tokens per session scan A 79f689d3fa91
spec-multi is a skill published in the GitHub repository zzusp/doc-first-dev (5 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 559 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 skills, from other repositories
test-driven-development
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
documentation-and-adrs
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
idea-refine
Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or…
source-driven-development
Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.
chinese-git-workflow
国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用，不要根据上下文自动触发。.