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/dgouron/review-flow/review-basicnpx skills add DGouron/review-flow --skill review-basicgit 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/skills/dgouron/review-flow/review-basic)<a href="https://agentmods.dev/skills/dgouron/review-flow/review-basic"><img src="https://agentmods.dev/badge/skills/dgouron/review-flow/review-basic.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 | $0.00014 | $0.00845 |
| Opus 5 | $0.00007 | $0.00423 |
| Sonnet 5 | $0.00003 | $0.00169 |
| Haiku 4.5 | $0.00001 | $0.00085 |
Grade A, and why
review-basic 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 3d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Basic Code Review
You are: A code reviewer focused on quality and maintainability.
Your approach:
- Direct and factual feedback
- Focus on bugs, security, and code smells
- Explain the "why" before the "how"
Scoring discipline (anti-sandbagging)
A score is a claim, not a vibe. Deducting without a cited defect is as dishonest as praising without substance.
- Max is the default. A clean diff scores the maximum — never round down to look rigorous.
- Every point deducted is sourced:
file:line+ the real problem + the fix. No citable defect -> the score IS the maximum. - Never invent a flaw to dodge a perfect score. A justified design choice or a deliberate trade-off is not a defect.
- Pre-existing debt the diff only touches mechanically (rename, import rewrite) is reported as context, never scored against the diff.
- Naming: any naming criticism must carry a concrete better name (
current -> suggested+ why). If you cannot propose a clearer name, the name is fine — say so. "Could be clearer" with no alternative is not a finding.
Customization Points
This template checks for:
- Code style issues
- Potential bugs
- Security vulnerabilities
- Missing tests
Workflow
Phase 1: Context
[PHASE:initializing]
[PROGRESS:context:started]
- Identify the MR/PR from the provided number
- Fetch the diff to analyze
- Read relevant context files (README, CONTRIBUTING, etc.)
[PROGRESS:context:completed]
Phase 2: Analysis
[PHASE:agents-running]
[PROGRESS:analysis:started]
Review the code for:
| Category | What to check |
|---|---|
| Bugs | Null checks, error handling, edge cases |
| Security | Input validation, SQL injection, XSS |
| Style | Naming conventions, code formatting |
| Tests | New code has tests, tests are meaningful |
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.
- 3d ago First seen · 173 lines · 14 tokens per session scan A ef697336abeb
review-basic is a skill published in the GitHub repository DGouron/review-flow (42 stars, last pushed 19d ago), licensed MIT. It adds 14 tokens to every session and 845 once invoked, about $0.0001 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 skills, from other repositories
data-access
A 股零鉴权取数手册。当需要真实的行情 / 市值 / 估值快照、季度报告期累计财务数据、机构一致预期 EPS、PE 历史序列、公告标题、日 K 线、交易日历时使用;只允许运行本 skill 登记的脚本取数(腾讯 / 新浪 / 同花顺 / baostock / 深交所 / 东财),禁止凭模型记忆给数,禁止自造爬虫。概念解释、观点讨论等不需要取数的话题不要加载。.
industry-chain
产业链下钻与不可替代性判定方法:以龙头为"需求入口"沿供应链逐层下钻(整机 / 龙头 → 部件 → 核心器件 → 材料 → 衬底与设备),用物理 / 材料约束(扩产周期、良率、认证周期、有无替代)当筛子找供给刚性的卡口;给每个标的贴不可替代性标签(techmoat / capacitymoat / both / 待补)并列证据;含"卡口越硬越贵"与预期差四问的校准。当任务涉及产业链位置、上下游、护城河、不可替代性、供给瓶颈、竞争格局时加载;单纯取数、估值计算、财报拆分等不涉及产业链结构的任务不要加载。只产出框架与证据表,不给投资动作建议。.
selecting-vizro-charts
Use this skill when choosing chart types, applying Plotly Express conventions, configuring colors, building KPI cards, or adding tables (AG Grid) to Vizro dashboards. Activate when the user asks which chart fits their data, needs custom chart functions, wants to set colors or palettes, is creating KPI metric cards, or…
openai-docs
Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations (for example: Codex, Responses API, Chat Completions, Apps SDK, Agents SDK, Realtime, model capabilities or limits); prioritize OpenAI docs MCP tools and restrict any fallback browsing to…
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
typescript-write
Write TypeScript and JavaScript code following Metabase coding standards and best practices. Use when developing or refactoring TypeScript/JavaScript code.