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/js-mark/skills/plan-featuregit clone --depth 1 https://github.com/JS-mark/skillsWhat 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.00014 | $0.00554 |
| Opus 5 | $0.00007 | $0.00277 |
| Sonnet 5 | $0.00003 | $0.00111 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
plan-feature 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.
What it actually says
执行步骤
步骤一：收集需求
使用 AskUserQuestion 向用户确认：
- 功能的具体描述和用户场景
- 是否有参考实现或设计稿
- 优先级和时间约束
步骤二：加载项目上下文
- 读取
CLAUDE.md获取项目架构和模板规范 - 使用 Glob 和 Grep 搜索与功能相关的现有代码：
- 搜索相似功能的实现模式
- 搜索可能需要修改的文件
- 搜索可复用的组件、服务、类型
- 读取关键文件了解当前实现
步骤三：架构分析
确定以下架构要素：
- 涉及进程: Main / Renderer / 两者
- IPC 通信: 是否需要新增 IPC channel（如是，必须遵循 6 步模板）
- 状态管理: 是否需要新建/扩展 Zustand store
- 持久化: 是否需要 Electron store 存储
- i18n: 是否需要新增翻译 key（en + zh）
- 流式数据: 是否涉及流式传输（EventEmitter + webContents.send）
步骤四：设计技术方案
输出：
- 数据流向图
- 关键接口/类型定义
- 需要的架构决策及推荐方案
- 可复用的现有组件/服务
步骤五：拆解 TODO
生成分阶段的任务清单：
Phase 1: 基础设施
- [ ] P0 任务描述（具体可执行）
Phase 2: 集成层
- [ ] P1 任务描述
Phase 3: UI 层
- [ ] P1 任务描述
Phase 4: 收尾
- [ ] P2 任务描述
每个 TODO 必须：
- 具体可执行（不能是「实现功能」这样笼统的描述）
- 标注优先级（P0/P1/P2）
- 标注涉及的文件路径
步骤六：保存方案
使用 AskUserQuestion 确认是否将方案保存到文件：
- 保存到
docs/plans/<feature-name>.md - 或仅在对话中展示
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 · 76 lines · 14 tokens per session scan A db8c2c5968bf
plan-feature is a command published in the GitHub repository JS-mark/skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 554 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-31.
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.