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-statusgit 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-status)<a href="https://agentmods.dev/skills/lordmos/dev-crew/crew-status"><img src="https://agentmods.dev/badge/skills/lordmos/dev-crew/crew-status/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-status"><img src="https://agentmods.dev/badge/skills/lordmos/dev-crew/crew-status.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.00022 | $0.00348 |
| Opus 5.5 | $0.00009 | $0.00139 |
| Sonnet 5.5 | $0.00004 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
crew.status 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 status — 查看工作区状态
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.
展示当前 DevCrew 工作区的概览：活跃变更、各变更所处阶段、进度和待解决的 blocker。
何时使用
- 用户说"看看进度"、"什么状态"、"show status"
- 新会话开始时恢复上下文
- 需要了解当前有哪些活跃变更
使用方法
CLI
npx @lordmos/dev-crew status
MCP Tool
crew_status(cwd: string)
输出内容
resume.md中的编排状态摘要- 每个活跃变更的名称和当前阶段（Plan/Design/Execute/Verify）
- 打开的 blocker 数量
阶段判定逻辑
根据变更目录中的文件存在性判定当前阶段：
test-report.md 存在 → Verify
impl-log.md 存在 → Execute
design.md 存在 → Design
仅 proposal.md → Plan
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 · 59 lines · 22 tokens per session scan A 893ad41a2b6d
crew.status is a skill published in the GitHub repository lordmos/dev-crew (11 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 348 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
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
remove
Remove a deployed framework or addon from the current workspace.