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 agentmods add commands/studyzy/tapd-ai-cli/speckit.implementgit clone --depth 1 https://github.com/studyzy/tapd-ai-cliWhat 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.00015 | $0.02245 |
| Opus 5 | $0.00008 | $0.01123 |
| Sonnet 5 | $0.00003 | $0.00449 |
| Haiku 4.5 | $0.00002 | $0.00225 |
Grade A, and why
speckit.implement 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 2d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
用户输入
$ARGUMENTS
在继续之前, 你必须考虑用户输入(如果不为空).
概要
-
从仓库根目录运行
.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks并解析 FEATURE_DIR 和 AVAILABLE_DOCS 列表. 所有路径必须是绝对路径. 对于参数中的单引号如 "I'm Groot", 使用转义语法: 例如 'I'''m Groot'(或尽可能使用双引号: "I'm Groot"). -
检查清单状态(如果 FEATURE_DIR/checklists/ 存在):
-
扫描 checklists/ 目录中的所有清单文件
-
对于每个清单, 统计:
- 总项目数: 所有匹配
- [ ]或- [X]或- [x]的行 - 已完成项目数: 匹配
- [X]或- [x]的行 - 未完成项目数: 匹配
- [ ]的行
- 总项目数: 所有匹配
-
创建状态表:
| Checklist | Total | Completed | Incomplete | Status | |-----------|-------|-----------|------------|--------| | ux.md | 12 | 12 | 0 | ✓ PASS | | test.md | 8 | 5 | 3 | ✗ FAIL | | security.md | 6 | 6 | 0 | ✓ PASS | -
计算总体状态:
- PASS: 所有清单都有 0 个未完成项目
- FAIL: 一个或多个清单有未完成项目
-
如果任何清单未完成:
- 显示包含未完成项目数的表格
- 停止并询问: "某些检查清单未完成. 是否仍要继续实施? (是/否)"
- 在继续之前等待用户响应
- 如果用户说 "否" 或 "等待" 或 "停止", 停止执行
- 如果用户说 "是" 或 "继续" 或 "执行", 继续到步骤 3
-
如果所有清单都已完成:
- 显示显示所有清单通过的表格
- 自动继续到步骤 3
-
-
加载和分析实施上下文:
- 必需: 读取 tasks.md 获取完整任务列表和执行计划
- 必需: 读取 plan.md 获取技术栈, 架构和文件结构
- 如果存在: 读取 data-model.md 获取实体和关系
- 如果存在: 读取 contracts/ 获取 API 规范和测试要求
- 如果存在: 读取 research.md 获取技术决策和约束
- 如果存在: 读取 quickstart.md 获取集成场景
-
项目设置验证:
- 必需: 基于实际项目设置创建/验证忽略文件:
检测和创建逻辑:
-
检查以下命令是否成功以确定是否为 git 仓库(如果是, 创建/验证 .gitignore):
git rev-parse --git-dir 2>/dev/null -
检查 Dockerfile* 是否存在或 plan.md 中是否提到 Docker → 创建/验证 .dockerignore
-
检查 .eslintrc* 是否存在 → 创建/验证 .eslintignore
-
检查 eslint.config.* 是否存在 → 确保配置的
ignores条目覆盖所需模式 -
检查 .prettierrc* 是否存在 → 创建/验证 .prettierignore
-
检查 .npmrc 或 package.json 是否存在 → 创建/验证 .npmignore(如果发布)
-
检查 terraform 文件(*.tf)是否存在 → 创建/验证 .terraformignore
-
检查是否需要 .helmignore(存在 helm charts)→ 创建/验证 .helmignore
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.
- 2d ago First seen · 133 lines · 15 tokens per session scan A 0a414ee41df5
speckit.implement is a command published in the GitHub repository studyzy/tapd-ai-cli (54 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 2,245 once invoked, about $0.0001 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-30.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.