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 instructions/morodomi/dev-crew/agents-mdgit 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.00971 | $0.00971 |
| Opus 5 | $0.00485 | $0.00485 |
| Sonnet 5 | $0.00194 | $0.00194 |
| Haiku 4.5 | $0.00097 | $0.00097 |
Grade A, and why
dev-crew AGENTS.md 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dev-crew
AI development team as a single Claude Code plugin.
Start Here
- Read CONSTITUTION.md for principles and docs/workflow.md for development flow
- Check docs/STATUS.md and
docs/cycles/for active work - If an
IN_PROGRESScycle exists, continue it; otherwise start withspec
Tech Stack
- Target Languages: PHP, Python, TypeScript, JavaScript, Flutter, Hugo
- Security: OWASP Top 10, CWE Top 25
Skills
Skills available: spec, red, green, refactor, review, commit, orchestrate, diagnose, onboard, sync-skills, skill-maker, cycle-retrospective, codify-insight, learn, evolve, security-scan, attack-report, context-review, generate-e2e, security-audit, php-quality, python-quality, ts-quality, js-quality, flask-quality, flutter-quality, hugo-quality, careful
Quick Start
# Run all structure validation tests
for f in tests/test-*.sh; do bash "$f"; done
# Run a specific test
bash tests/test-plugin-structure.sh
TDD Workflow
spec → plan-review → approve → /orchestrate (sync-plan → pre-red-gate → RED → GREEN → REFACTOR → REVIEW → cycle-retrospective → pre-commit-gate → COMMIT)
Cycle docs: docs/cycles/YYYYMMDD_HHMM_<topic>.md
Post-Approve Action
plan review（Claude 設計レビュー + Codex利用可能時は competitive review）は承認前の spec 内（Step 8）で完了済み。Plan mode を抜けたら /orchestrate を起動する。Edit/Write は直接行わず、必ず /orchestrate に委譲する（プロンプトベースの規律。hook による強制ブロックではない）。
Quality Standards
| Metric | Target |
|---|---|
| Test coverage | 90%+ (min 80%) |
| Static analysis | 0 errors |
| Test design | Given/When/Then |
| SKILL.md | < 100 lines |
Key Constraints
| Constraint | Rule |
|---|---|
| SKILL.md | < 100 lines. Detail goes in reference.md (Progressive Disclosure) |
| Agents | Markdown with YAML frontmatter (name, description, model, tools?). read-only agent は tools で Read/Grep/Glob に限定、writer は tools 省略で全継承。例外: dast-crawler は Playwright MCP のツール名制約（未設定環境で起動拒否）のため tools 省略で全継承（writer ではない）。memory を持つ agent は必ず disallowedTools: Write, Edit を併記する（memory 併用時は tools 宣言外の Write が有効化されるため） |
| Cycle docs | docs/cycles/YYYYMMDD_HHMM_description.md |
| Git | <type>: <subject> (feat/fix/docs/refactor/test/chore) |
| Tests | All changes require passing tests before commit |
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 · 85 lines · 971 tokens per session scan A b43242273551
dev-crew AGENTS.md is an instructions file published in the GitHub repository morodomi/dev-crew (1 stars, last pushed 3d ago), licensed MIT. It adds 971 tokens to every session, about $0.0049 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 instructions, from other repositories
nuxt-supabase-starter CLAUDE.md
Instructions for YuDefine/nuxt-supabase-starter, covering claude.md, language, project structure and meta vs template 邊界.
arc AGENTS.md
Instructions for howells/arc, covering arc, shape, gotchas, editing constraints and search order.
gem-team AGENTS.md
Instructions for mubaidr/gem-team, covering agents.md, project overview, key features, setup commands and install apm (agent package manager).
specs-driven-development-spring-angular always-on.instructions.md
Always-on guardrails for spec-driven Spring + Angular development.
specs-driven-development-spring-angular production-code.instructions.md
Production code guardrails — TDD discipline and Spring Boot 4 conventions.
specs-driven-development-spring-angular frontend-code.instructions.md
Frontend code guardrails for Angular implementation, testing, and accessibility.