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/handoffgit 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/handoff)<a href="https://agentmods.dev/commands/yezannnnn/agentgroup/handoff"><img src="https://agentmods.dev/badge/commands/yezannnnn/agentgroup/handoff.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.00604 |
| Opus 5 | $0.00000 | $0.00302 |
| Sonnet 5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
handoff 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
/handoff - 设计交付
整理设计稿，准备交付给贾维斯开发
使用方式
/handoff [设计稿名称]
/handoff 登录页面
/handoff all # 交付所有待开发设计
执行步骤
1. 检查设计完整性
确认设计稿包含：
- 页面布局（ASCII图示）
- 设计规范（颜色、字体、间距）
- 组件状态（默认、hover、active、disabled）
- 交互说明
- 异常状态处理
2. 生成开发交付文档
# 设计交付 - [功能名称]
## 交付信息
设计师: 艾拉
交付日期: YYYY-MM-DD
设计稿位置: ../shared/designs/[文件名].md
## 设计概览
[简要说明设计内容]
## 开发注意事项
### 关键交互
1. [重要交互点1]
2. [重要交互点2]
### 组件复用
| 组件 | 是否复用 | 参考 |
|------|----------|------|
| 按钮 | 是 | 现有Button组件 |
| 表单 | 是 | 现有Form组件 |
| 卡片 | 新建 | 见设计稿 |
### 响应式要求
| 断点 | 布局变化 |
|------|----------|
| < 768px | 单列布局 |
| >= 768px | 双列布局 |
## 验收标准
1. 还原度达到设计稿要求
2. 交互效果流畅
3. 异常状态处理完善
## 设计稿清单
- [ ] [设计稿1].md
- [ ] [设计稿2].md
3. 更新共享状态
更新 ../shared/status.json：
{
"designs": {
"[功能名]": {
"status": "待开发",
"designer": "艾拉",
"files": ["xxx-ui.md", "xxx-prototype.md"],
"handoffDate": "YYYY-MM-DD"
}
}
}
4. 通知选项
询问用户：
- 是否需要通知贾维斯开始开发？
- 如需通知，我会在status.json中标记任务
交付检查清单
| 检查项 | 状态 |
|---|---|
| 颜色值完整 | ✓ |
| 字号字重完整 | ✓ |
| 间距标注完整 | ✓ |
| 交互说明清晰 | ✓ |
| 异常状态定义 | ✓ |
| 响应式说明 | ✓ |
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 · 98 lines · 0 tokens per session scan A 8435d6328a36
handoff 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 604 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.