story-full-exec

story-full-exec is a command for Claude Code from snakeying/Textum. It costs 0 tokens per session (795 once invoked), scanned A, original, MIT.

A batch command for executing several numbered software work items, called Stories, from their YAML instruction files.

In plain words
What is it for?
Use it to run Stories in a chosen order, apply their code and tests, run their verification commands, and collect failures.
Why use it?
It avoids running each Story by hand and gives one final PASS or FAIL summary. It checks all required files first and continues with later Stories when one fails.

Command for Claude Code

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/story-full-exec
Clone the repo
git clone --depth 1 https://github.com/snakeying/Textum

Made for: Claude Code.

Wrote 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.

agentmods badge for story-full-exec

README.md
[![agentmods](https://agentmods.dev/badge/commands/snakeying/textum/story-full-exec.svg)](https://agentmods.dev/commands/snakeying/textum/story-full-exec)
Your own site
<a href="https://agentmods.dev/commands/snakeying/textum/story-full-exec"><img src="https://agentmods.dev/badge/commands/snakeying/textum/story-full-exec.svg" alt="Measured on agentmods" height="20"></a>
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 795 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00795
Opus 5 $0.00000 $0.00398
Sonnet 5 $0.00000 $0.00159
Haiku 4.5 $0.00000 $0.00080

Measured 5d ago against content hash cdf277f9ef31, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

story-full-exec 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 5d 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.

outdated/.claude_outdated/commands/story-full-exec.md · 46 lines

What it actually says

阶段6c: Story 批量执行(实验 / story-full-exec)

  • $ARGUMENTS: Story 编号列表(仅支持 / 分隔,例如:1/2/3

读取:docs/story-<n>-exec-pack.yaml(每个 n;唯一事实来源;必须存在) | 写入:仓库文件(代码/测试;多个 Story) | 模板:N/A

按指定顺序依次执行多个 Story,并在末尾汇总 FAIL

输入解析(必须)

  • $ARGUMENTS 解析为编号序列 N_list
    • 格式必须为:<n1>/<n2>/...(只允许正整数与 /;不允许空格)
    • / 分割;保留输入顺序;去重(保留首次出现)
    • 每个编号必须为正整数;否则输出 FAIL 并停止(不执行任何 Story)
    • N_list 解析后不得为空;否则输出 FAIL 并停止(不执行任何 Story)

全量前置检查(必须;fail-fast)

  • N_list 中每个 ndocs/story-<n>-exec-pack.yaml 必须存在
  • 若任一缺失:输出 FAIL 清单(每个缺失 pack 1 条;需明确缺失的 docs/story-<n>-exec-pack.yaml)并停止(不执行任何 Story)

执行规则(继续执行;不回滚)

  • 对多个 Story 依次执行并一次性汇总输出;不逐个等待人工验收

N_list 按顺序逐个执行:

  1. 执行:
    • 对每个 n:按 /story <n> 的硬约束与步骤执行(docs/story-<n>-exec-pack.yaml 为唯一事实来源;禁止再读取/通读 docs/PRD.md / docs/GLOBAL-CONTEXT.md / docs/story-*.md
    • 验证命令:按 pack 的 verification.commands 执行;gate:* / opt:* 各只跑 1 次;失败不重试
    • 若出现阻断(pack 不足/矛盾、验收未达成、任一 gate:* FAIL):记录 FAIL,但继续执行下一个 Story

输出(低噪;一次性汇总)

  • 若在“输入解析”或“全量前置检查”阶段出现 FAIL:只输出 FAIL 清单并停止(不执行任何 Story)
  • 总结论:
    • 若任一 Story 出现 FAIL → 输出 FAIL
    • 否则 → 输出 PASS
  • 执行摘要(每个 Story 仅 1 行):
    • Story <n>: PASS
    • Story <n>: FAIL
  • 若存在任何 FAIL:输出 FAIL 清单(F-001 起编号;每条必须包含:定位/问题/期望/影响/修复;且 修复 只给 1 个动作)
  • 若存在需要用户确认的非阻断项:输出 DECISION 清单(D-001 起编号;每条包含:问题 / 影响 / 建议动作)
  • 末尾追加:
    • 修正:按 FAIL 清单逐条修复后重跑 /story-full-exec <原参数>
    • 重跑:/story-full-exec <原参数>
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.

  1. 5d ago First seen · 46 lines · 0 tokens per session scan A cdf277f9ef31

Subscribe to this mod's changes

story-full-exec 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 795 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.