code-review-standards

A code-review skill that finds team rules stored in a repository’s `.forge-review/` folder and applies them during reviews. The folder can contain general, security, and language-specific standards.

In plain words
What is it for?
Use it when reviewing a repository that has `.forge-review/` configuration. It can load review settings, ignored files, and standards for languages such as Go, Python, and TypeScript.
Why use it?
It keeps reviews aligned with the project’s own expectations instead of relying only on generic coding advice. It also lets teams keep review rules next to their code.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/initializ/forge/code-review-standards
Any agent
npx skills add initializ/forge --skill code-review-standards
Clone the repo
git clone --depth 1 https://github.com/initializ/forge

Made for: Claude Code, Codex.

Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,337 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00018 $0.01337
Opus 5 $0.00009 $0.00668
Sonnet 5 $0.00004 $0.00267
Haiku 4.5 $0.00002 $0.00134

Measured 2d ago against content hash 542c816c4dd9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-review-standards 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 2d 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.

forge-skills/local/embedded/code-review-standards/SKILL.md · 210 lines

How it starts

The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Code Review Standards

Teaches the agent to discover and apply organization-specific coding standards stored in a .forge-review/ directory in the target repository. This skill provides configuration templates and standard rule files that teams can customize.

Overview

The .forge-review/ directory is a convention for storing code review configuration alongside the codebase. When present, the code-review skill automatically loads these standards and applies them during reviews.

This skill:

  • Documents the .forge-review/ directory structure and file formats
  • Provides templates for bootstrapping review standards in new repositories
  • Teaches the agent how to discover and interpret standards files

Directory Structure

.forge-review/
├── config.yaml                  # Review configuration
├── .forge-review-ignore         # Files/patterns to skip during review
└── standards/                   # Coding standards (one file per topic)
    ├── general.md               # General coding rules
    ├── security.md              # Security rules
    ├── go.md                    # Go-specific rules
    ├── python.md                # Python-specific rules
    ├── typescript.md            # TypeScript rules
    └── testing.md               # Testing rules

Tool: review_standards_init

Initialize a .forge-review/ directory in the current repository with default templates.

This is a binary-backed tool that uses filesystem operations (mkdir, write) to scaffold the standards directory. The agent reads templates bundled with this skill and writes them to the target repository.

Input:

Parameter Type Required Description
target_dir string no Target directory (default: current working directory)
languages array no Language-specific standards to include: go, python, typescript. Default: all
overwrite boolean no Overwrite existing files. Default: false

Output: List of created files and a summary of the initialized configuration.

Read the full file on GitHub · 210 lines

Changes

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.

  1. 2d ago First seen · 210 lines · 18 tokens per session scan A 542c816c4dd9

Subscribe to this mod's changes

code-review-standards is a skill published in the GitHub repository initializ/forge (156 stars, last pushed 5d ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,337 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.