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/split)<a href="https://agentmods.dev/commands/snakeying/textum/split"><img src="https://agentmods.dev/badge/commands/snakeying/textum/split/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/split"><img src="https://agentmods.dev/badge/commands/snakeying/textum/split.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.02011 |
| Opus 5.5 | $0.00000 | $0.00804 |
| Sonnet 5.5 | $0.00000 | $0.00402 |
| Haiku 4.5 | $0.00000 | $0.00201 |
Grade A, and why
split 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
阶段3: Story 拆分（/split）
读取：docs/split-plan.yaml、docs/PRD.md（只读）、docs/GLOBAL-CONTEXT.md（只读） | 写入：docs/story-*-*.md | 模板：.claude/textum/story-template.md
按 split-plan 生成 Story 文件（含 YAML front-matter）。
最小读取范围（必须；避免通读）
- split-plan：全量（用于 Story 边界 / 模块 / 依赖 / API 分配）
- GC：仅第 4 节业务规则表（用于挑选可用
BR-###写入refs.gc_br） - PRD：
5.2 功能规格：按模块抽取FP-001与功能点描述（用于 Story 的 FP 分配与“功能点”章节）6. 业务规则：仅当需要写入refs.prd_br时，按需抽取可引用的BR-###8.0 功能点→落点映射：用于把FP-001映射到本 Story 必须声明的refs.prd_tbl[]/artifacts.*[]8.1 表清单：用于校验/选择可用TBL-###（如适用）9.2 接口清单：仅用于确认接口 ID 集合（Story 的refs.prd_api来自 split-plan 分配）
硬约束
- 不得更改
docs/split-plan.yaml的 Story 编号/边界/API 分配：若发现不合理则停止并输出阻断原因（不写 Story 文件；需要先修正 split-plan） - 每个 Story 文件必须包含 YAML front-matter（文件首部
--- ... ---），且字段齐全、可解析（结构以模板为准） - 每个 Story 文件不得出现 fenced code blocks（```）
- YAML front-matter 中所有 ID 必须为具体数字：
modules[]:M-01fp_ids[]:FP-001refs.gc_br[]/refs.prd_br[]:BR-001refs.prd_tbl[]:TBL-001refs.prd_api[]:API-001
- Story 模板章节不得缺失；无内容写
N/A；不得残留占位符（如TBD、[功能描述]、M-xx、FP-###、Story N） - 验收标准不得留空：
## 验收标准（必填）章节下必须存在- [ ]条目，且每条必须包含非空描述（不得整行仅为- [ ] 技术验收:/- [ ] 用户验收:，也不得为N/A）
- 若
docs/split-plan.yaml的api_assignments为空（无 API）：- 每个 Story front-matter
refs.prd_api必须为空数组 - 每个 Story 的
## 接口章节正文必须严格为 1 行N/A
- 每个 Story front-matter
FP 分配规则（必须；机械可执行）
- 定义
P_fp：从 PRD### 8.0 功能点→落点映射（必填）表第一列抽取全部FP-001，升序排序 - 定义
P_fp_by_module[M-xx]：从 PRD5.2各模块小节的「功能点」表抽取FP-001（保留在P_fp中的），按FP升序排序 - 若任一
FP-001在 PRD5.2的多个模块小节出现：停止并提示修正 PRD（保证 FP 唯一归属一个模块） - 对每个模块
M-xx：- 定义
S(M-xx)：split-plan 中stories[]里modules包含该M-xx的 Story 列表（按n升序） - 若
S(M-xx)为空：停止并提示修正 split-plan（必须覆盖该模块） - 将
P_fp_by_module[M-xx]依序按 round-robin 分配给S(M-xx)：第 i 个 FP →S(M-xx)[(i-1) mod |S(M-xx)|]
- 定义
- 对每个 Story：
fp_ids =分配给该 Story 的 FP 并集（升序）；不得为空 - 全局一致性：所有 Story 的
fp_ids并集必须与P_fp完全一致（无遗漏/无重复归属）
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 · 93 lines · 0 tokens per session scan A 4e9fe1064ff6
split 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,011 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.