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/peterfei/ai-agent-team/fe-startgit clone --depth 1 https://github.com/peterfei/ai-agent-teamWrote 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/peterfei/ai-agent-team/fe-start)<a href="https://agentmods.dev/commands/peterfei/ai-agent-team/fe-start"><img src="https://agentmods.dev/badge/commands/peterfei/ai-agent-team/fe-start.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.00022 | $0.00406 |
| Opus 5 | $0.00011 | $0.00203 |
| Sonnet 5 | $0.00004 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
fe-start 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
前端开发 - 线程工作流
此命令会创建独立线程并立即以前端开发工程师身份开始工作。
使用方法
/fe-start "开发登录表单组件"
注意：请务必提供任务描述。请勿在输入
/fe-start后直接回车，否则将创建无标题任务。
⚠️ 重要：执行流程
第1步：创建线程
调用 mcp__thread-manager__create_thread：
{
title: "[用户提供的任务标题]",
description: "前端开发任务 - [任务标题]",
tags: ["frontend", "fe"],
switchTo: true
}
第2步：简洁通知
只输出一行：
✨ 已创建前端线程："[标题]" (ID: [前8位])
第3步：立即开始前端工作 ⭐
不要停止！立即切换到前端开发角色并开始工作：
- 读取
.claude/agents/frontend_dev.md - 以前端开发工程师的身份和能力工作
- 输出完整的组件设计/代码实现
- 就像用户直接调用了
/fe [任务]一样
示例
用户: /fe-start "开发登录表单组件"
Claude:
✨ 已创建前端线程："开发登录表单组件" (ID: abc12345)
---
## 前端组件设计 - 登录表单
### 组件结构
...
### 代码实现
...
[立即开始完整的前端开发工作]
等价于：/start-task fe "开发登录表单组件"
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 · 78 lines · 0 tokens per session scan A edb7d31830a1
fe-start is a command published in the GitHub repository peterfei/ai-agent-team (429 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 406 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
skill-inbox
Unified entry point for managing skill suggestions and browsing all installed skills. Provides two views: suggestions (default) and all skills.
eval-merge
Use the Read tool to load .skill-compass/{skill-name}/manifest.json. Verify.
cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].
cti-status
Health check — backend tier, case store, MCP tools, API credit balances. Run this when something behaves oddly. Usage: /cti-status.
reskin
Extract a measured design signature (type ramp, accent + its budget, grid unit, radius, layout) from a reference image or site, write it to signature.json, and drive the build to match it — "steal this vibe" as a spec, not pixels.
enum-udp
UDP scan + service follow-up — top ports first, full sweep only when justified.