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/yezannnnn/agentgroup/plangit clone --depth 1 https://github.com/yezannnnn/agentGroupWrote 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/yezannnnn/agentgroup/plan)<a href="https://agentmods.dev/commands/yezannnnn/agentgroup/plan"><img src="https://agentmods.dev/badge/commands/yezannnnn/agentgroup/plan.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 | $0.00000 | $0.00264 |
| Opus 5 | $0.00000 | $0.00132 |
| Sonnet 5 | $0.00000 | $0.00053 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
plan 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 4d 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
/plan - 制定技术方案
根据PRD或需求输出技术方案
使用方式
/plan [PRD文件路径或需求描述]
执行步骤
-
阅读PRD/需求，理解功能要求
-
分析技术选型和实现方案
-
输出技术方案文档，包含：
# 技术方案 - [功能名称]
## 1. 需求概述
简述PRD核心要求
## 2. 技术选型
- 前端: xxx
- 后端: xxx
- 数据库: xxx
- 其他: xxx
## 3. 架构设计
整体架构说明 + 图示（如需要）
## 4. 接口设计
### API列表
| 接口 | 方法 | 说明 |
|-----|------|-----|
### 接口详情
...
## 5. 数据结构
表结构/模型定义
## 6. 实现步骤
1. xxx
2. xxx
## 7. 风险评估
潜在问题和应对方案
-
存储到
../shared/tasks/plans/目录 -
询问用户是否调整或开始开发
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.
- 4d ago First seen · 52 lines · 0 tokens per session scan A dfe14ac0e725
plan is a command published in the GitHub repository yezannnnn/agentGroup (149 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 264 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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.