consistency-review

consistency-review is a skill for Claude Code from mnthe/hardworker-marketplace. It costs 40 tokens per session (3,366 once invoked), scanned A, original, MIT.

A review checklist for checking whether code follows the same names, styles, patterns, and project rules throughout a codebase.

In plain words
What is it for?
Use it during planning or final review to check naming, repeated patterns, project standards, and documentation consistency.
Why use it?
It helps catch inconsistent code before a change is approved, especially when several developers worked on it.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions CLAUDE.md.

Part of the ultrawork plugin — 15 skills, 9 commands shipped together

Good fit Use it during planning or final review to check naming, repeated patterns, project standards, and documentation consistency.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mnthe/hardworker-marketplace/consistency-review
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.

Any agent
npx skills add mnthe/hardworker-marketplace --skill consistency-review
Clone the repo
git clone --depth 1 https://github.com/mnthe/hardworker-marketplace

Made for: Claude Code.

Or install ultrawork, the plugin that ships this one along with the rest of its 15 skills, 9 commands.

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.

agentmods badge for consistency-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/mnthe/hardworker-marketplace/consistency-review/github.svg)](https://agentmods.dev/skills/mnthe/hardworker-marketplace/consistency-review)
Your own site
<a href="https://agentmods.dev/skills/mnthe/hardworker-marketplace/consistency-review"><img src="https://agentmods.dev/badge/skills/mnthe/hardworker-marketplace/consistency-review/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.

agentmods 80×15 button for consistency-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/mnthe/hardworker-marketplace/consistency-review"><img src="https://agentmods.dev/badge/skills/mnthe/hardworker-marketplace/consistency-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,366 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.03366
Opus 5 $0.00020 $0.01683
Sonnet 5 $0.00008 $0.00673
Haiku 4.5 $0.00004 $0.00337

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

Security

Grade A, and why

consistency-review scanned grade A with 1 finding 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 11d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

const data1 = await fetch(url1);
plugins/ultrawork/skills/consistency-review/SKILL.md · 603 lines

How it starts

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

Consistency Review

Code consistency and project standards validation for ultrawork verification phase.

What This Skill Provides

Systematic approach to checking:

  • Naming conventions across the codebase
  • Code style consistency
  • Pattern adherence and repetition
  • Project-specific standards
  • Documentation consistency

When to Use This Skill

During VERIFICATION phase:

  • After workers complete tasks
  • Before marking tasks as complete
  • When multiple workers contribute to same feature
  • Before final approval

During PLANNING phase:

  • Validating design document format
  • Ensuring task naming consistency
  • Checking for adherence to project patterns

Naming Conventions

1. Variable and Function Names

Checklist:

[ ] Consistent naming style (camelCase, PascalCase, snake_case)
[ ] Descriptive names (not x, tmp, data)
[ ] Boolean variables prefixed (is, has, should, can)
[ ] Functions are verbs (get, set, create, update, delete)
[ ] Constants are UPPER_SNAKE_CASE
[ ] Private members prefixed/suffixed (_, $)
[ ] Abbreviations used consistently

Examples:

// ❌ Bad: Inconsistent naming
const UserData = "john";        // PascalCase for variable
function GetUser() {}           // PascalCase for function
const is_active = true;         // snake_case
const MAX_users = 100;          // Mixed case

// ✅ Good: Consistent naming
const userName = "john";        // camelCase
function getUser() {}           // camelCase
const isActive = true;          // camelCase, boolean prefix
const MAX_USERS = 100;          // UPPER_SNAKE_CASE

2. File and Directory Names

Checklist:

[ ] Consistent file naming (kebab-case or camelCase throughout)
[ ] Component files match component name
[ ] Test files follow naming convention (*.test.*, *.spec.*)
[ ] Index files used consistently
[ ] Directory structure follows project pattern

Common Patterns:

Language/Framework Convention Example
JavaScript/Node kebab-case user-service.js
React Components PascalCase UserProfile.jsx
TypeScript camelCase or kebab-case userService.ts
Tests Same as source + suffix user-service.test.js

Read the full file on GitHub · 603 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. 11d ago First seen · 603 lines · 40 tokens per session scan A 79a0780f544d

Subscribe to this mod's changes

consistency-review is a skill published in the GitHub repository mnthe/hardworker-marketplace (4 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 3,366 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.