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-initnpx skills add lordmos/dev-crew --skill crew-initgit 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.00030 | $0.02641 |
| Opus 5 | $0.00015 | $0.01321 |
| Sonnet 5 | $0.00006 | $0.00528 |
| Haiku 4.5 | $0.00003 | $0.00264 |
Grade A, and why
crew.init 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
crew.init — 初始化 DevCrew 工作区并激活协议
Pre-flight Check
Run the check.sh script in this skill's directory:
- If
STATUS: INITIALIZED→ Workspace already exists. Tell the user: "DevCrew 工作区已初始化，无需重复执行。可使用 /crew.status 查看当前状态。" Do not proceed. - If
STATUS: NOT_INITIALIZED→ Continue with initialization below.
初始化 DevCrew 多 Agent 协作工作区，并加载完整的团队编排协议。这是使用 DevCrew 的入口 Skill。
何时使用
- 从零开始一个新项目，需要 AI 团队协作
- 为已有项目引入 DevCrew 协议
- 用户说"初始化"、"设置 DevCrew"、"set up dev-crew"
使用方法
CLI（推荐）
npx @lordmos/dev-crew init [options]
参数：
| 选项 | 说明 | 示例 |
|---|---|---|
--platform, -p |
目标 AI 平台，自动写入平台指令文件 | --platform copilot |
--name |
项目名称（默认从 package.json 或目录名推断） | --name my-app |
--no-gitignore |
不修改 .gitignore |
平台选项：
crew init -p copilot # → .github/copilot-instructions.md
crew init -p cursor # → .cursorrules
crew init -p claude # → CLAUDE.md
crew init -p copilot cursor # 多平台
MCP Tool
crew_init(cwd: string, name?: string, platform?: string[], gitignore?: boolean)
创建的文件结构
your-project/
├── INSTRUCTIONS.md ← AI 行为指令（核心协议文件）
├── dev-crew.yaml ← 项目配置
└── dev-crew/
├── resume.md ← PjM 编排状态
├── blockers.md ← 问题与决策跟踪
├── specs/ ← 共享规约
├── memory/ ← Agent 长期记忆
│ ├── pdm.md
│ ├── architect.md
│ ├── implementer.md
│ ├── tester.md
│ └── reviewer.md
└── templates/ ← 文档格式模板
├── proposal.md
├── design.md
├── impl-log.md
├── test-report.md
└── review-report.md
幂等性
重复执行不会覆盖已有文件，只补全缺失部分。
DevCrew 协议（初始化后自动激活）
以下是初始化后 AI Agent 应遵循的完整 DevCrew 团队编排协议。
你是一个 DevCrew 驱动的 AI 软件开发团队的项目经理（PjM）。你负责编排和指挥多个专业 Agent，让它们各司其职、平行协作，共同完成用户的开发任务。用户只说做什么，你负责拆解任务、分配角色、协调进度。
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.
- 3d ago First seen · 212 lines · 30 tokens per session scan A ac56cbf0c455
crew.init is a skill published in the GitHub repository lordmos/dev-crew (10 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 2,641 once invoked, about $0.0002 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…