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.
git clone --depth 1 https://github.com/snakeying/TextumWrote 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/snakeying/textum/prd-check)<a href="https://agentmods.dev/commands/snakeying/textum/prd-check"><img src="https://agentmods.dev/badge/commands/snakeying/textum/prd-check/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/snakeying/textum/prd-check"><img src="https://agentmods.dev/badge/commands/snakeying/textum/prd-check.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.02178 |
| Opus 5.5 | $0.00000 | $0.00871 |
| Sonnet 5.5 | $0.00000 | $0.00436 |
| Haiku 4.5 | $0.00000 | $0.00218 |
Grade A, and why
prd-check 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 1mo 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
阶段1c: PRD 校验
读取：docs/PRD.md | 写入：无（只输出 FAIL/PASS；不修改文件） | 模板：N/A
输出 FAIL/PASS 清单；不修改任何文件。
输出规则（只读）
- 不输出 PRD 原文
- 若存在任何
FAIL：- 输出
FAIL清单（F-001起编号；每条必须包含以下字段）：定位：章节路径 +（尽量）稳定ID（BR-###/FP-###/TBL-###/API-###）或锚点（<!-- PRD#... -->）；避免行号问题：1 句期望：可机械执行的“替换目标/格式”（能推导就写出来）影响：H/M/L修复：只给 1 个动作（通常是“把本 FAIL 清单粘贴给 /prd 并按定位逐条修正” + 本条的最小修改点）
- 末尾追加：
修正：将 FAIL 清单作为可选输入粘贴给 /prd，逐条修正 docs/PRD.md重跑：/prd-check
- 然后结束
- 输出
- 否则（无
FAIL）：输出PASS，并在末尾追加：下一步：/scaffold
FAIL 校验项（机械性门禁）
0) 文件存在
docs/PRD.md必须存在
1) 结构完整性（不得缺章）
必须包含以下一级章节（缺失即 FAIL）：
## 1. 项目概述## 2. 范围与假设## 3. 目标用户与角色## 4. 权限矩阵（必填）## 5. 核心功能## 6. 业务规则（必填）## 7. 状态与枚举（必填）## 8. 数据模型（必填）## 9. 接口设计（必填）## 10. 非功能需求（必填，可写 N/A）
2) 模板占位符（不得残留）
PRD 中不得出现 fenced code blocks（```）；出现即 FAIL。
全文不得残留任何模板占位符；命中即 FAIL。
机械拦截（任一命中即 FAIL）：
TBD[...]PRD#API-###/PRD#TBL-###/PRD#BR-###API-###/TBL-###/BR-###（仍为###占位）FP-###（仍为###占位）A/D/O4XX/5XX
2.5) 角色与权限最小可用性
- PRD
### 3.1 用户角色必须包含表格，且至少 1 行数据 - PRD
## 4. 权限矩阵（必填）必须包含表格，且至少 1 行数据 - PRD
## 4. 权限矩阵（必填）中每行权限必须严格为A/D/O之一
3) 稳定ID（接口/表）一致性
接口（如适用；无 API 必须写 N/A）
先判断 PRD 是否有接口（必须按 N/A_STRICT 判定）：
N/A_STRICT 判定口径（权威；逐字一致；禁止改写）：
- 定位 PRD 小节
### 9.2 接口清单（必填）的正文（标题行之后到下一同级小节标题之前） - 判定
N/A_STRICT = true当且仅当：正文去掉空行并 Trim 后仅剩 1 行且该行严格等于N/A
据此：若 N/A_STRICT = true 则 PRD_HAS_API = false；否则 PRD_HAS_API = true。
若 PRD_HAS_API = false：
- 第 9 节
9.1/9.2/9.3三个小节正文必须全部满足N/A_STRICT（仅一行N/A；不得残留表格/子标题/其它文本） - PRD 中不得出现任何
API-###/API-001或<!-- PRD#API-... -->
若 PRD_HAS_API = true：
- PRD
9.2 接口清单：必须至少 1 条接口；每条接口必须有且仅有一个API-###，且必须是具体数字（API-001形式）；禁止缺失/重复/仍为API-### - PRD
9.3 接口详情：每个详情标题必须包含对应的API-### - PRD
9.3 接口详情：每个接口详情标题行必须以#### 9.3.开头（标题级别/前缀固定） - PRD
9.3 接口详情：每个详情标题行必须包含对应的锚点<!-- PRD#API-### -->（具体数字：<!-- PRD#API-001 -->形式），且锚点<ID>必须与标题中的API-###一致；禁止缺失/仍为PRD#API-### - 一致性：
9.2中出现的每个API-###都必须在9.3有对应详情；9.3中出现的API-###也必须在9.2清单中存在
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.
- 1mo ago First seen · 116 lines · 0 tokens per session scan A c3504ce0d0ae
prd-check is a command published in the GitHub repository snakeying/Textum (41 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,178 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-30.
Other commands, from other repositories
statuswt
You are checking the status of all active worktree task files in the project.
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.