What is split-check1?

A validation command for checking whether a software project’s Story-splitting plan and Story files are structurally consistent.

Use it to inspect the split plan and Story documents, write a check index when they pass, or produce a repair list when they fail.

It catches missing references, inconsistencies, and threshold or gate failures before implementation continues.

split-check1 — Command by snakeying

Install

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.

agentmods

npx agentmods add commands/snakeying/textum/split-check1

Clone the repo

git clone --depth 1 https://github.com/snakeying/Textum

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 3,336 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.03336
Opus 5	$0.00000	$0.01668
Sonnet 5	$0.00000	$0.00667
Haiku 4.5	$0.00000	$0.00334

Measured yesterday against content hash 22ee322dd720, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

split-check1 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.

outdated/.claude_outdated/commands/split-check1.md · 194 lines

How it starts

The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.

阶段4a: Story 拆分校验（Core / split-check1）

读取：docs/split-plan.yaml、docs/story-*-*.md | 写入：docs/split-check-index-pack.yaml（仅无 FAIL；PASS/DECISION 都写） | 模板：.claude/textum/split-check-index-pack-template.yaml

做“结构/一致性/阈值”校验。

输出（DECISION 不阻断）

若存在任何 FAIL（含阈值 FAIL 与门禁 FAIL）：
- 输出 FAIL 清单（F-001 起编号；每条必须包含以下字段）：
  - 定位：目标文件（docs/split-plan.yaml 或 docs/story-N-<slug>.md）+（尽量）YAML 路径/章节名/指标名；避免行号
  - 问题：1 句
  - 期望：可机械执行的“替换目标/格式”（能推导就写出来）
  - 影响：H/M/L
  - 修复：只给 1 个动作（通常是“按定位修正对应文件”或“将 SPLIT_REPLAN_PACK 粘贴给 /split-plan 重规划”）
- 若包含阈值 FAIL：紧接着追加且仅追加 1 个 SPLIT_REPLAN_PACK 代码块
- 末尾追加：
  - 修正：按 FAIL 清单逐条修复（若包含 SPLIT_REPLAN_PACK：将其粘贴给 /split-plan 重规划；否则修正 docs/story-*-*.md 或 docs/split-plan.yaml）
  - 重跑：/split-check1
- 然后结束（不写 pack）
否则（无 FAIL）：
- 写入 docs/split-check-index-pack.yaml
- 若存在任何 DECISION：输出 DECISION 清单（D-001 起编号；每条包含：问题 / 影响 / 建议动作），并在末尾追加：
  - 已写入：docs/split-check-index-pack.yaml
  - 下一步：/split-check2
- 否则：输出：
  - PASS
  - 已写入：docs/split-check-index-pack.yaml
  - 下一步：/split-check2

执行步骤（必须按序）

解析 docs/split-plan.yaml（只抽取索引）：
- stories[]：story、n、slug、modules[]、prereq_stories[]
- api_assignments[]：api、story
解析所有 docs/story-*-*.md（只抽取索引 + 机械计数）：
- 解析 YAML front-matter（文件首部 --- ... ---），抽取：
  - story/n/slug/title
  - modules/prereq_stories/fp_ids
  - refs.gc_br/refs.prd_br/refs.prd_tbl/refs.prd_api
  - artifacts.file/artifacts.cfg/artifacts.ext
- 计数口径：
  - api_refs = refs.prd_api 去重后数量
  - tbl_refs = refs.prd_tbl 去重后数量
  - feature_points = fp_ids 去重后数量
  - acceptance_items = ## 验收标准（必填） 章节下 - [ ] 条目数
大 Story 阈值（早期短路）：
- 若任一 Story 命中阈值 FAIL：输出 FAIL + SPLIT_REPLAN_PACK 并结束（不写 pack）
- 否则：记录阈值 DECISION（若有），继续执行门禁
执行门禁（见下）
生成索引交接包（见下），写入 docs/split-check-index-pack.yaml

大 Story 阈值（早期短路）

机械计数口径（必须一致）

对每个 docs/story-N-*.md：

api_refs：YAML front-matter refs.prd_api 去重数量
tbl_refs：YAML front-matter refs.prd_tbl 去重数量
feature_points：YAML front-matter fp_ids 去重数量
acceptance_items：## 验收标准（必填） 章节下 - [ ] 条目数

Read the full file on GitHub · 194 lines

Changes

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 · 194 lines · 0 tokens per session scan A 22ee322dd720

Subscribe to this mod's changes

split-check1 is a command published in the GitHub repository snakeying/Textum (41 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,336 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.

Planning Writing and docs claude-code claude-skill codex codex-skill skills vibe-coding

split-check1

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

阶段4a: Story 拆分校验（Core / split-check1）

输出（DECISION 不阻断）

执行步骤（必须按序）

大 Story 阈值（早期短路）

机械计数口径（必须一致）

What this file has done since we first saw it

Other commands, from other repositories

ask

ask

planwt

statuswt

finishwt

checklist