Borrowing it
Nothing to install: this file belongs to Goktug/ai-crew. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Goktug/ai-crew/main/CLAUDE.mdgit clone --depth 1 https://github.com/Goktug/ai-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/instructions/goktug/ai-crew/claude-md)<a href="https://agentmods.dev/instructions/goktug/ai-crew/claude-md"><img src="https://agentmods.dev/badge/instructions/goktug/ai-crew/claude-md.svg" alt="Measured on agentmods" 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.01108 | $0.01108 |
| Opus 5 | $0.00554 | $0.00554 |
| Sonnet 5 | $0.00222 | $0.00222 |
| Haiku 4.5 | $0.00111 | $0.00111 |
Grade A, and why
ai-crew CLAUDE.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 7d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ai-crew
Production-grade Claude Code plugin: takes any React Native or TypeScript backend task from idea to PR with one human checkpoint.
Design (locked)
All eight architectural decisions are locked. Do not propose changes to any of: model routing, dispatch tiers, artifact set, vendor strategy, or lifecycle phases without explicit approval.
Source of truth
reference-projects/agent-skills/ — base. Will be vendored verbatim (one-time copy) into skills/, agents/, references/, hooks/, and .claude/commands/ at the plugin root. Never edit vendored files.
Model routing
| Layer | Model | Role |
|---|---|---|
team-lead (main session) |
Fable 5 | Coordinator — plans big, executes small. Orchestrator + architect + planner + verifier + reviewer + shipper. Heavy thinking inline; never reads token-heavy raw material a dispatch can read. |
sonnet-developer / opus-developer / fable-developer subagents |
Sonnet / Opus / Fable 5 | One task per dispatch, routed by the plan's complexity flag (simple / complex / frontier). fable-developer is rare by design — no rate arbitrage, only context isolation and depth. No Agent/Task tool. |
web-researcher subagent |
Haiku | One focused web-research question per dispatch. No Agent/Task tool. |
Architectural laws (non-negotiable)
- Strict 1-level dispatch. Subagents never spawn subagents.
- Reference-based dispatch with line-range citations. Subagent prompts contain task IDs, skill paths, and line-range citations into
spec.mdandplan.md— never embedded content and never whole-file pointers.spec.mdcarries a Section Index andplan.mdcarries a Task Index; every developer dispatch includes aPlan taskrange and at least oneSpec refsrange so the subagent reads only the slices it needs. - Three-file disk artifacts per run:
spec.md,plan.md,progress.md. Nothing else unless materially needed. - Run state at
~/.claude/ai-crew/runs/<YYYY-MM-DD-slug>/. - Vendored agent-skills SKILL.md content is never edited. One-time copy, no upstream sync.
- Plan quality > parallelism. Atomized DAG with per-task acceptance criteria + verification commands. Sonnet executes mechanically when the plan is right.
- No reviewer subagents. Fable team-lead does five-axis review inline using agent-skills' four review skills (
code-review-and-quality,security-and-hardening,code-simplification,performance-optimization). - Verify/review retry policy: max 3 fix loops before escalating to user.
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.
- 7d ago First seen · 72 lines · 1,108 tokens per session scan A 30898ddf21cd
ai-crew CLAUDE.md is an instructions file published in the GitHub repository Goktug/ai-crew (6 stars, last pushed 1mo ago), licensed MIT. It adds 1,108 tokens to every session, about $0.0055 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
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.