Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/s977043/PlanGatenpx agentmods add commands/s977043/plangate/codex-mvp-splitWrote 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/s977043/plangate/codex-mvp-split)<a href="https://agentmods.dev/commands/s977043/plangate/codex-mvp-split"><img src="https://agentmods.dev/badge/commands/s977043/plangate/codex-mvp-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/s977043/plangate/codex-mvp-split"><img src="https://agentmods.dev/badge/commands/s977043/plangate/codex-mvp-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.00718 |
| Opus 5.5 | $0.00000 | $0.00287 |
| Sonnet 5.5 | $0.00000 | $0.00144 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
codex-mvp-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.
What it actually says
/codex-mvp-split
規模 L 以上の機能を着手する前段で、最小 MVP (Phase 1) を Codex に選定相談する。属人化された Phase 分割質問を標準化 (TASK-0118 / #352)。
正本:
docs/ai/codex-mvp-split.md前段連携:docs/ai/plan-metrics-verification.md(#351 / TASK-0117) で「規模 L 以上」判定された場合に本コマンド起動を推奨
引数
<topic> — MVP 分割を検討する機能・トピック名。
いつ使うか
- A フェーズ (PBI INPUT PACKAGE 作成) 前段
- TASK-0117 事前メトリクス検証で 実数 / 見積もり ≥ 3 倍 (規模 L 相当) と判定された場合
- 1 セッションで全部実装すると完結しない規模の機能
質問テンプレ (Codex へ)
<project> の「<topic>」の最小 MVP 設計について Codex に相談します。
# 背景
<関連既存機能 + ギャップ + 直近文脈>
# 質問
**質問**: 「<topic>」の Phase 1 最小 MVP は次のどれが妥当か?
(A) 新ページ独立案
(B) 既存拡張案
(C) 最小新規導線案
(D) Codex 独自案
工数感 (S/M/L) と推奨理由を 400 字程度で。判断材料となる
「ユーザ価値」「実装の独立性」「次フェーズへの拡張性」を含めてください。
採用後
PBI INPUT PACKAGE に Phase 分割表 を必ず含める:
| Phase | 内容 | 工数 | 状態 |
|---|---|---|---|
| 1 | <採用案> | M | 着手 |
| 2 | <次の拡張> | S | 繰延 |
| 3 | <最終形> | M | 繰延 |
Phase 1 を本セッションの PBI scope とし、Phase 2 以降は繰延 (別 PBI)。
出力
- Codex 回答 (4 選択肢から 1 つ + 工数 + 3 軸の判断材料)
- PBI INPUT PACKAGE への Phase 分割表
関連
- 正本:
docs/ai/codex-mvp-split.md - skill:
.agents/skills/codex-mvp-split/SKILL.md - 前段: TASK-0117 (#351) 事前メトリクス検証
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 · 59 lines · 0 tokens per session scan A 0e8a694e6f65
codex-mvp-split is a command published in the GitHub repository s977043/PlanGate (2 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 718 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-09-03.
Other commands, from other repositories
execute-parallel-status
Retired parallel status table; use cli-hierarchy (RFC-0051) instead. See docs/operations/cli-hierarchy.md. AISDLC-763.
start-development
Start development workflow process in Moira.
backlog
Generate prioritised product backlog from ArcKit artifacts - convert requirements to user stories, organise into sprints.
service-assessment
Prepare for GDS Service Standard assessment - analyze evidence against 14 points, identify gaps, generate readiness report.
story
Generate comprehensive project story with timeline analysis, traceability, and governance achievements (project).
data-mesh-contract
Create federated data product contracts for mesh architectures with SLAs, governance, and interoperability guarantees (project).