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 skills add lordmos/dev-crew --skill crew-agentsgit clone --depth 1 https://github.com/lordmos/dev-crewWrote 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/skills/lordmos/dev-crew/crew-agents)<a href="https://agentmods.dev/skills/lordmos/dev-crew/crew-agents"><img src="https://agentmods.dev/badge/skills/lordmos/dev-crew/crew-agents/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/lordmos/dev-crew/crew-agents"><img src="https://agentmods.dev/badge/skills/lordmos/dev-crew/crew-agents.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00034 | $0.00468 |
| Opus 5.5 | $0.00014 | $0.00187 |
| Sonnet 5.5 | $0.00007 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
crew.agents 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 1mo 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 agents — 列出可用领域专家
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.
查看所有可用的领域专家（Domain Specialists），了解每位专家的名称、所属领域和适用的 PDEVI 阶段。
何时使用
- 用户问"有哪些专家"、"list agents"、"谁能帮忙"
- 需要为特定领域（如安全、游戏开发）激活专家
- 配置
dev-crew.yaml前了解选项
使用方法
CLI
npx @lordmos/dev-crew agents
MCP Tool
crew_agents()
输出内容
按领域分组展示所有可用专家：
- 专家 ID：用于
dev-crew.yaml配置 - 专家名称：角色描述
- 适用阶段：在 PDEVI 的哪些阶段参与
激活专家
在 dev-crew.yaml 中添加专家 ID：
specialists:
- game-designer
- security-engineer
- devops-engineer
激活后，PjM 会在对应 PDEVI 阶段自动调度专家参与协作。
可用领域
游戏开发（8）· UI/UX（3）· 安全（1）· DevOps（3）· 测试（3）· 工程（5）· 数据（2）· AI/ML（1）· Web3（1）· 空间计算（2）
共 29 位领域专家覆盖 10 个领域。
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.
- 1mo ago First seen · 69 lines · 34 tokens per session scan A 947571e92ae5
crew.agents is a skill published in the GitHub repository lordmos/dev-crew (11 stars, last pushed 6mo ago), licensed MIT. It adds 34 tokens to every session and 468 once invoked, about $0.0001 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.