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/initializ/forge/code-review-standardsnpx skills add initializ/forge --skill code-review-standardsgit clone --depth 1 https://github.com/initializ/forgeWhat 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.00018 | $0.01337 |
| Opus 5 | $0.00009 | $0.00668 |
| Sonnet 5 | $0.00004 | $0.00267 |
| Haiku 4.5 | $0.00002 | $0.00134 |
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.
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.
What ships with it
8 files 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.
- templates/.forge-review/.forge-review-ignore 571 B
- templates/.forge-review/config.yaml 1.1 KB
- templates/.forge-review/standards/general.md 1.4 KB
- templates/.forge-review/standards/go.md 2.3 KB
- templates/.forge-review/standards/python.md 2.2 KB
- templates/.forge-review/standards/security.md 2.4 KB
- templates/.forge-review/standards/testing.md 2.5 KB
- templates/.forge-review/standards/typescript.md 2.5 KB
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.
- 2d ago First seen · 210 lines · 18 tokens per session scan A 542c816c4dd9
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.
Other skills, from other repositories
mistake-reflection
Use when you discover you made a mistake — caught by the user, by a tool result, by your own re-reading, or by a failed check. Appends a structured entry to docs/ai/ailearnings.md and re-reads recent entries to avoid repeats.
quality-loop
Use this workflow recipe when a draft, plan, proposal, or other deliverable should be independently reviewed and revised until it satisfies explicit quality criteria.
mcporter
Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, CLI/type generation, and MCP-backed skills that need a durable command path.
openai-whisper-api
Transcribe audio via OpenAI Audio Transcriptions API (Whisper).
plan_route
Plan a route and return distance + ETA (schema + deterministic result).
recommend_poi
Recommend a POI in a city (schema + deterministic result).