What is convention-checker?

A project-specific checker that reviews changed files against the repository's documented coding standards.

Use it after editing several application or service files, or when preparing a commit, to check imports, exports, naming, types, comments, and area-specific conventions.

It catches style and architecture violations before code is committed, including rules that differ between frontend, backend, services, packages, and tests.

How AlexisBalayre/claude-code-power-config configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to AlexisBalayre/claude-code-power-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/AlexisBalayre/claude-code-power-config/main/.claude/agents/convention-checker.md

Clone the repo

git clone --depth 1 https://github.com/AlexisBalayre/claude-code-power-config

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/alexisbalayre/claude-code-power-config/convention-checker/github.svg)](https://agentmods.dev/agents/alexisbalayre/claude-code-power-config/convention-checker)

Your own site

<a href="https://agentmods.dev/agents/alexisbalayre/claude-code-power-config/convention-checker"><img src="https://agentmods.dev/badge/agents/alexisbalayre/claude-code-power-config/convention-checker/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/agents/alexisbalayre/claude-code-power-config/convention-checker"><img src="https://agentmods.dev/badge/agents/alexisbalayre/claude-code-power-config/convention-checker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 56 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 434 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00056	$0.00434
Opus 5	$0.00028	$0.00217
Sonnet 5	$0.00011	$0.00087
Haiku 4.5	$0.00006	$0.00043

Measured 10d ago against content hash 7c6b69f7c59e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

convention-checker 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 10d 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.

.claude/agents/convention-checker.md · 40 lines

What it actually says

Project Convention Auditor

Verify the specified files against the project's strict architectural and style guidelines. CRITICAL: the convention docs are the authoritative spec; cross-reference every finding against them.

1. Contextual Mapping

Map each file path to its area doc:

apps/acme-api/ → docs/conventions/backend.md
apps/acme-web/ → docs/conventions/frontend.md
services/acme-session-engine/ → docs/conventions/services.md
services/acme-gateway/ → docs/conventions/services.md
packages/acme-providers/ → docs/conventions/services.md
packages/acme-db/ → docs/conventions/backend.md
packages/acme-rpc/ → docs/conventions/services.md
**/*.test.ts → docs/conventions/testing.md

2. Load the spec

Read docs/conventions/core.md plus the mapped area doc for each file under review. Those documents are the authoritative spec; do not rely on memorized rules. Apply the universal rules from core.md (exports, imports, JSDoc, comments, type safety, naming) and the area-specific obligations from the mapped doc to every file.

3. Pattern Matching

Read 2-3 existing files in the same directory to identify and verify local structural patterns (e.g., specific dependency-injection styles or error-handling blocks).

Reporting Format

For each violation, provide:

Location: path/to/file.ts:L123
Rule Violated: The specific guideline from the convention doc.
Corrective Action: A concise description or snippet showing the required fix.

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.

10d ago First seen · 40 lines · 56 tokens per session scan A 7c6b69f7c59e

Subscribe to this mod's changes

convention-checker is an agent published in the GitHub repository AlexisBalayre/claude-code-power-config (2 stars, last pushed 29d ago), licensed MIT. It adds 56 tokens to every session and 434 once invoked, about $0.0003 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.

Claude Code Code review agents ai anthropic claude developer-tools

code-reviewer

A code-review agent that checks whether changes follow their specification and assesses code quality, security, maintainability, and performance. It reports findings with severity levels and file-and-line references.

sangrokjung/claude-forge · 96 tokens

security-reviewer

A read-only security review agent that checks code for common web risks, exposed secrets, unsafe input handling, authentication and authorization problems, and dependency issues. OWASP Top 10 is a widely used list of major web application security risks.

sangrokjung/claude-forge · 95 tokens

adversarial-reviewer

Independent read-only checker for behavioural changes. Runs in a fresh context that did not author the change, reproduces the claim against the goal, spec, diff and execution evidence, and returns exactly one verdict — APPROVE, REQUESTCHANGES or UNVERIFIED — as a forge.review/v1 envelope. MUST BE USED before claiming…

sangrokjung/claude-forge · 102 tokens

database-reviewer

Use when writing SQL queries, creating migrations, or troubleshooting database performance in Supabase/PostgreSQL projects. Reviews indexes, RLS policies, schema types, N+1 patterns. Read-only reviewer with EXPLAIN ANALYZE capability.

sangrokjung/claude-forge · 52 tokens

refactor-cleaner

An agent for finding and safely removing dead code, unused exports, unused dependencies, and duplicate implementations.

sangrokjung/claude-forge · 109 tokens

skeptical-auditor

Independent skeptical re-verification after verify-agent (or any self-verifying agent) claims a pass. Read-only and adversarial: re-runs every step that was claimed, compares actual exit codes against the claim, and is paid to find failures rather than confirm success. Never approves without executed evidence. Spawned…

sangrokjung/claude-forge · 120 tokens

claude-code-power-config: Agent for Claude Code