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/morodomi/dev-crew/commitnpx skills add morodomi/dev-crew --skill commitgit clone --depth 1 https://github.com/morodomi/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.00034 | $0.01325 |
| Opus 5 | $0.00017 | $0.00662 |
| Sonnet 5 | $0.00007 | $0.00265 |
| Haiku 4.5 | $0.00003 | $0.00133 |
Grade A, and why
commit 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 yesterday.
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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow
Cycle Doc Gate
for f in docs/cycles/*.md; do [ -f "$f" ] || continue; fm=$(awk '/^---$/{c++;next} c==1{print}' "$f"); echo "$fm" | grep -q '^phase:' || continue; echo "$fm" | grep -q 'phase: DONE' && continue; printf '%s\t%s\n' "$(echo "$fm" | awk 'sub(/^updated: */,""){gsub(/T/," ");print;exit}')" "$f"; done | sort | tail -1 | cut -f2 → found: continue / not found: BLOCK(run spec)
Phase Ordering Gate: Progress Log に REVIEW の Phase completed 記録があるか確認。なければ BLOCK: 「先に review を実行してください」
Test List Completion Gate: Test List の TODO/WIP/DISCOVERED に未完了項目(- [ ] TC-)が残っていれば BLOCK。DISCOVERED残項目は review の DISCOVERED→Issue 処理に戻す。詳細: reference.md
Progress Log Completeness Gate: Progress Log に RED/GREEN/REFACTOR/REVIEW の全4フェーズの Phase completed 記録があるか確認。不足フェーズがあれば BLOCK。詳細: reference.md
Pre-COMMIT Gate (deterministic)
Cycle doc の Progress Log を確認し、以下が全て満たされなければ BLOCK:
- REVIEW完了: Progress Log に
### ... - REVIEWセクションがあり、Phase completed記録がある - Codex review記録 (
which codex成功時のみ): Progress Log にCodex+reviewの記録がある - retro_status check: retro_status: captured / resolved で PASS。none で BLOCK (cycle-retrospective 実行)、field 不在は WARN のみで PASS (legacy compat)
# 1. REVIEW チェック(phaseヘッダーにアンカー)
awk '/^### .* - REVIEW/,/Phase completed/' "$CYCLE_DOC" | grep -qi 'Phase completed'
# 2. Codex review チェック(codex利用可能時のみ)
which codex && grep -qiE 'Codex.*review|codex.*Review' "$CYCLE_DOC"
いずれか失敗 → BLOCK(不足ステップを案内)
STATUS.md同期警告 (非BLOCK): ls tests/test-*.sh | wc -l と STATUS.md の Test Scripts 値を比較。不一致なら警告表示。
Step 2: 変更確認 + Pre-commit Hook
git status && git diff --stat
ls .husky/pre-commit .git/hooks/pre-commit 2>/dev/null
Step 3: ドキュメント更新
| ドキュメント | 条件 | 更新内容 |
|---|---|---|
| Cycle doc | 常に | phase: DONE, Progress Log に COMMIT 記録 |
| STATUS.md | 常に | 完了タスクを Completed に移動 |
| README.md | skills/ or agents/ 変更時 | スキル一覧・構成の更新 |
| AGENTS.md | skills/ or agents/ 変更時 | cross-toolセクションの更新 |
| CLAUDE.md | skills/ or agents/ 変更時 | Skills セクションの更新 |
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.
- yesterday First seen · 94 lines · 34 tokens per session scan A 2f66cf2a95cc
commit is a skill published in the GitHub repository morodomi/dev-crew (1 stars, last pushed 3d ago), licensed MIT. It adds 34 tokens to every session and 1,325 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
software-test-execution
Run scoped tests for a TDD slice, determine the appropriate test framework and command, and report structured pass/fail results. Use when tests need to be executed after writing, implementing, or refactoring code. Reads test metadata, discovers the test framework if needed, executes the scoped test command, parses…
nw-at-completeness-check
Canonical AT completeness gate — research-anchored 7-category taxonomy (C1-C7) + 15-item mechanical checklist. Paradigm-neutral. Drives acceptance-designer reviewer verdict deterministically.
nw-ab-critique-dimensions
Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation.
nw-bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
software-code-refactoring
Improve production code quality while preserving all existing test behavior. Commonly used for the Refactor phase of TDD red-green-refactor, but applicable to any codebase with tests. Use when production code works but needs cleanup — reducing duplication, improving naming, simplifying complexity, aligning with…
nw-canary
Canary skill for auto-injection detection.