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/zhmxiaowo/opencode-simple/specgit clone --depth 1 https://github.com/zhmxiaowo/opencode-simpleWhat 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.00023 | $0.00421 |
| Opus 5 | $0.00012 | $0.00211 |
| Sonnet 5 | $0.00005 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
spec 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 — Spec-First 快捷方式
/plan的轻量版本 — 只输出 SPEC 部分，跳过实施步骤分解。
说明
/spec 与 /plan 共享同一个 planner agent 和同一套 Spec-First 流程（MCP 文档研究 → SPEC 输出 → 等待确认），区别仅在于：
| 命令 | 输出内容 |
|---|---|
/plan |
SPEC + 实施步骤 + 风险评估（完整） |
/spec |
仅 SPEC（API 设计、数据模型、依赖、编译计划） |
工作流程
- 需求确认 — 提取功能名称、技术栈、核心需求
- MCP 文档研究 — 并行调用
context7（官方文档）+exa-web-search（社区实践） - 输出 SPEC — 生成包含以下章节的规范文档：
- API / 接口设计（精确到可直接复制到代码）
- 数据模型
- 依赖项及版本
- 编译验证计划（具体命令）
- 已知限制 & 兼容性
- 参考文档链接
- 等待确认 — 必须等用户明确确认后方可编码
参数
/spec Unity PlayerController/spec Cocos 2D骨骼动画/spec UE5 Gameplay Ability System/spec React Dashboard
何时用 /spec，何时用 /plan
- 小功能 / 单文件改动 →
/spec足够 - 多文件 / 跨模块 / 需要分阶段实施 → 用
/plan（包含 SPEC + 完整步骤）
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 · 43 lines · 23 tokens per session scan A 2e518d3a52a5
spec is a command published in the GitHub repository zhmxiaowo/opencode-simple (2 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 421 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.