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 skills/lordmos/dev-crew/crew-plannpx skills add lordmos/dev-crew --skill crew-plangit clone --depth 1 https://github.com/lordmos/dev-crewWhat 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.00028 | $0.00566 |
| Opus 5 | $0.00014 | $0.00283 |
| Sonnet 5 | $0.00006 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
crew.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 2d 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
crew plan — 创建变更计划
Pre-flight Check
Run the check.sh script in this skill's directory:
- If
STATUS: NOT_INITIALIZED→ Stop. Tell the user: "DevCrew 工作区尚未初始化，请先运行 /crew.init" - If
STATUS: INITIALIZED→ Use the output as workspace context. Proceed below.
创建一个新的变更（change），自动推断工作模式，进入 PDEVI 工作流的 Plan 阶段。
何时使用
- 用户描述了一个新需求、功能或修复
- 用户说"开始做"、"新建变更"、"create a change"
- 需要从需求→设计→实现→验证的完整流程
使用方法
CLI
npx @lordmos/dev-crew plan <name> [options]
参数：
| 选项 | 说明 | 示例 |
|---|---|---|
<name> |
变更名称（kebab-case） | add-auth-middleware |
-d, --description |
变更描述 | -d "为 API 添加 JWT 认证" |
-m, --mode |
工作模式 | -m express |
MCP Tool
crew_plan(cwd: string, name: string, description?: string, mode?: "standard" | "express" | "prototype")
模式推断
未显式指定模式时，自动推断：
| 信号 | 推断模式 |
|---|---|
| 描述含 fix / bug / hotfix / patch | Express（P → E → V） |
| 描述含 spike / prototype / poc | Prototype（P → D → E） |
| 其他 | Standard（P → D → E → V → I） |
创建的文件
dev-crew/changes/<name>/
├── proposal.md ← PdM 需求文档（含验收标准）
└── design.md ← Architect 技术方案（Express 模式不创建）
下一步
Plan 创建后，PdM 填写 proposal.md 的需求和验收标准，等待用户确认后进入下一阶段。
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 72 lines · 28 tokens per session scan A 4b4501483168
crew.plan is a skill published in the GitHub repository lordmos/dev-crew (10 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 566 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.