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/designgit 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/design)<a href="https://agentmods.dev/commands/yezannnnn/agentgroup/design"><img src="https://agentmods.dev/badge/commands/yezannnnn/agentgroup/design.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.00526 |
| Opus 5 | $0.00000 | $0.00263 |
| Sonnet 5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
design 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 5d 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
/design - UI设计
根据PRD需求设计用户界面
使用方式
/design [PRD文件或功能描述]
/design 登录页面
/design ../shared/docs/xxx.md
执行步骤
1. 理解需求
- 读取PRD文档或用户描述
- 提取关键功能点和用户流程
- 确认设计范围（移动端/PC端）
2. 确认设计方向
询问用户：
- 是否有参考设计？
- 是否沿用现有设计规范？
- 有特殊风格要求吗？
3. 输出设计稿
# UI设计 - [功能名称]
## 设计信息
设计师: 艾拉
日期: YYYY-MM-DD
PRD来源: [来源]
## 设计规范
### 颜色
| 名称 | 色值 | 用途 |
|------|------|------|
| 主色 | #1890FF | 按钮、链接 |
| 背景 | #F5F5F5 | 页面背景 |
| 文字 | #333333 | 主要文字 |
### 字体
| 类型 | 字号 | 字重 | 颜色 |
|------|------|------|------|
| 大标题 | 24px | 600 | #333 |
| 标题 | 18px | 500 | #333 |
| 正文 | 14px | 400 | #666 |
### 间距
| 类型 | 数值 |
|------|------|
| 页面边距 | 16px |
| 模块间距 | 24px |
| 元素间距 | 12px |
## 页面布局
### [页面名称]
+----------------------------------+
| Header 44px |
+----------------------------------+
| |
| [内容区域描述] |
| |
+----------------------------------+
| Footer 50px |
+----------------------------------+
### 组件说明
[各组件的详细说明]
## 交互说明
[用户操作流程和反馈]
4. 存储设计稿
保存到 ../shared/designs/[功能名]-ui.md
5. 询问后续
- 是否需要调整？
- 是否通知贾维斯开始开发？
示例
输入: /design 接待建档页面
输出: 完整的UI设计稿，包含布局、规范、交互说明
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.
- 5d ago First seen · 92 lines · 0 tokens per session scan A df70a7094267
design 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 526 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
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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.