Borrowing it
Nothing to install: this file belongs to DGouron/review-flow. 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/DGouron/review-flow/master/CLAUDE.mdgit clone --depth 1 https://github.com/DGouron/review-flowWrote 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/dgouron/review-flow/claude-md)<a href="https://agentmods.dev/instructions/dgouron/review-flow/claude-md"><img src="https://agentmods.dev/badge/instructions/dgouron/review-flow/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.04062 | $0.04062 |
| Opus 5 | $0.02031 | $0.02031 |
| Sonnet 5 | $0.00812 | $0.00812 |
| Haiku 4.5 | $0.00406 | $0.00406 |
Grade A, and why
review-flow 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 — 427 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ReviewFlow CLAUDE.md
Quick start
New here? Read docs/HARNESS-ONBOARDING.md first — covers the 5 key commands, active hooks, and the SDD pipeline.
Behavior
Important: Each response will start with "I read the rules." This demonstrates you have followed our guidelines.
Always challenge me when relevant and be straightforward without sugarcoating.
Always evaluate the scope of what's being asked and tell me if it's too broad or vague.
Since I'm allergic to technical comments in code, only add them if vital for understanding. This means you've already named functions, files, variables, and folders in a way that screams intent.
Language Rules
- Documentation: English
- Technical (code, tests, commits, logs): English
Project Overview
ReviewFlow is an AI-powered code review automation tool for GitLab/GitHub using Claude Code. It receives webhooks from merge requests/pull requests, queues review jobs, invokes Claude for automated code review, and posts inline comments and review reports back to the platform.
Check package.json for all package versions.
Development Commands
Essential Commands
yarn dev # Start dev server (tsx watch)
yarn build # Build TypeScript + resolve aliases + copy assets
yarn start # Start production server
yarn typecheck # TypeScript validation only
yarn lint # Oxlint check
yarn lint:fix # Auto-fix linting issues
yarn format # Format with oxfmt
yarn format:check # Check formatting without writing
# Testing
yarn test # Run tests with UI
yarn test:ci # Run tests in CI mode
yarn coverage # Generate coverage report
# Quality
yarn verify # Run typecheck + lint + test:ci (run before commits)
# Documentation
yarn docs:dev # VitePress dev server
yarn docs:build # Build docs
yarn docs:preview # Preview built docs
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 · 427 lines · 4,062 tokens per session scan A 5b1f45129eb6
review-flow CLAUDE.md is an instructions file published in the GitHub repository DGouron/review-flow (42 stars, last pushed 4d ago), licensed MIT. It adds 4,062 tokens to every session, about $0.0203 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-30.
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.