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.
npx skills add xtyooo/specpilot-codex --skill specpilot-confirmgit clone --depth 1 https://github.com/xtyooo/specpilot-codexWrote 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/skills/xtyooo/specpilot-codex/specpilot-confirm)<a href="https://agentmods.dev/skills/xtyooo/specpilot-codex/specpilot-confirm"><img src="https://agentmods.dev/badge/skills/xtyooo/specpilot-codex/specpilot-confirm.svg" alt="Measured on agentmods" 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.00049 | $0.01391 |
| Opus 5 | $0.00024 | $0.00696 |
| Sonnet 5 | $0.00010 | $0.00278 |
| Haiku 4.5 | $0.00005 | $0.00139 |
Grade A, and why
specpilot-confirm 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 7d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecPilot: 需求确认
分析用户填写的原始需求，识别模糊点和边界条件，提出疑问等待用户确认，确认后整理最终需求文档。
参数
the user-provided arguments after the command text- 要确认的需求编号（如 REQ-001）
规则约束
- 必须先读取项目指南：
docs/specpilot/project-guide.md - 必须先读取需求草稿再开始分析
- 原始需求内容必须保留，不可删除或修改
- 提出的问题要全面、具体、有针对性
- 必须进行完整数据链路分析，追踪数据从输入到最终处理的完整流程
- 确认完成后才更新需求文档
执行步骤
阶段一：准备
- 从
the user-provided arguments after the command text解析需求编号（去除空格） - 如果未提供编号，运行
ls docs/specpilot/requirements/并询问用户要确认哪个需求 - 读取草稿文件：
docs/specpilot/requirements/REQ-{编号}-draft.md - 读取项目指南：
docs/specpilot/project-guide.md - 更新
docs/specpilot/requirements/index.md：将状态改为🔍 confirming
阶段二：需求分析（深度分析）
深入分析需求内容，必须识别以下问题：
2.1 基础分析
- 术语定义：是否有需要明确定义的术语或概念？
- 边界条件：是否有未说明的边界情况？
- 业务规则：是否有隐含的业务规则需要明确？
- 数据定义：涉及的数据字段、格式、来源是否清晰？
- 状态流转：如有状态变化，流转规则是否完整？
- 异常处理：异常情况如何处理？
- 关联影响：是否影响其他功能或模块？
- 前置条件：是否有前置依赖或假设？
2.2 完整数据链路分析（重要）
必须分析完整的数据/调用链路：
- 数据流向：数据从哪里来？经过哪些处理？最终到哪里？
- 调用链路：涉及哪些方法/服务？调用顺序是什么？
- 时序依赖：是否有异步处理？存储和使用的时序是否正确？
- 数据合并：更新数据时是否会覆盖其他字段？
- MQ/异步：如果涉及消息队列，消费端能否获取到所需数据？
2.3 技术可行性分析
- 现有代码：读取相关代码文件，分析现有实现
- 接口格式：如涉及外部接口，确认数据格式是否符合规范
- 字段命名：确认字段名称是否与官方文档/规范一致
阶段三：提出疑问
- 将分析出的所有疑问整理成清晰的问题列表
- 按重要程度排序，严重问题优先
- 输出格式：
## 需求分析
我已阅读需求内容并进行了完整数据链路分析，有以下问题需要确认：
### 关键问题（必须确认）
1. **[问题类别]**：[具体问题描述]？
- 背景：[为什么这是个问题]
- 建议：[如果有建议方案]
### 一般问题
2. **[问题类别]**：[具体问题描述]？
...
### 技术确认点
- [需要用户确认的技术细节]
...
请逐一回答上述问题，我会在确认后整理最终需求。
- 等待用户逐一回答问题
- 如有新的疑问，继续追问直到所有细节明确
- 对于复杂需求，可能需要多轮确认
阶段四：整理最终需求
用户确认完所有问题后：
- 将原始需求和确认结果整理成结构化的最终需求
- 更新草稿文件
REQ-{编号}-draft.md，结构如下：
# REQ-{编号}-[描述]
> 状态：✅📋 已确认
---
## 【原始需求】
<!-- 原封不动保留用户最初填写的需求内容，仅作依据 -->
{用户原始填写的需求内容}
---
## 【需求确认】
<!-- AI分析确认后生成的结构化需求，实际设计和实施以此为准 -->
### 术语定义
| 术语 | 定义 |
|-----|------|
| xxx | xxx |
### 数据模型设计
[涉及的数据结构、字段定义]
### 业务规则
| 条件 | 处理 |
|-----|------|
| xxx | xxx |
### 数据流/调用链路
[完整的数据流向或调用链路说明]
### 边界条件
- [边界情况1]：[处理方式]
- [边界情况2]：[处理方式]
### 涉及代码文件
| 文件 | 修改内容 |
|-----|---------|
| xxx | xxx |
### 补充说明
[其他需要说明的内容]
---
## 【执行模式】
{保留原有选择}
---
## 【关联需求】
{保留原有内容}
---
## 【代码位置说明】
{保留原有内容}
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.
- 7d ago First seen · 195 lines · 49 tokens per session scan A 32fdc12d084b
specpilot-confirm is a skill published in the GitHub repository xtyooo/specpilot-codex (10 stars, last pushed 10d ago), licensed MIT. It adds 49 tokens to every session and 1,391 once invoked, about $0.0002 per session on Opus 5. 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.