Coherence Check

Coherence Check is a skill for Claude Code, Codex from reggiechan74/cc-plugins. It costs 77 tokens per session (3,252 once invoked), scanned A, original, MIT.

A review process that uses multiple agents with different review roles to check production-critical code. Production-critical code includes changes where failures could affect payments, security, data, deployments, or compliance.

In plain words
What is it for?
Use it for payment logic, authentication, security work, database migrations, production releases, regulatory code, and business data transformations. It coordinates planning and opposing reviews before the code is considered ready.
Why use it?
It reduces the chance that one reviewer misses an important problem. The process requires a plan and predefined acceptance checks before implementation.

Skill for Claude CodeCodex

Part of the code-coherence plugin — 5 skills, 7 agents shipped together

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/reggiechan74/cc-plugins/coherence-check
Any agent
npx skills add reggiechan74/cc-plugins --skill coherence-check
Clone the repo
git clone --depth 1 https://github.com/reggiechan74/cc-plugins

Made for: Claude Code, Codex.

Or install code-coherence, the plugin that ships this one along with the rest of its 5 skills, 7 agents.

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 Coherence Check

README.md
[![agentmods](https://agentmods.dev/badge/skills/reggiechan74/cc-plugins/coherence-check.svg)](https://agentmods.dev/skills/reggiechan74/cc-plugins/coherence-check)
Your own site
<a href="https://agentmods.dev/skills/reggiechan74/cc-plugins/coherence-check"><img src="https://agentmods.dev/badge/skills/reggiechan74/cc-plugins/coherence-check.svg" alt="Measured on agentmods" height="20"></a>
Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,252 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.00077 $0.03252
Opus 5 $0.00039 $0.01626
Sonnet 5 $0.00015 $0.00650
Haiku 4.5 $0.00008 $0.00325

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

Security

Grade A, and why

Coherence Check 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 4d 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.

code-coherence/skills/coherence-check/SKILL.md · 416 lines

How it starts

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

Coherence Check: Multi-Agent Verification

Purpose

Execute comprehensive multi-agent verification for production-critical code using the "Team of Rivals" architecture. This skill orchestrates specialized critic agents with opposing incentives to catch errors before they reach production, achieving 92%+ reliability versus 60% single-agent baseline.

When to Use

Activate this skill for high-stakes code where errors have significant consequences:

  • Financial calculations and payment processing
  • Authentication and security implementations
  • Database migrations and schema changes
  • Production deployments and releases
  • Regulatory compliance code
  • Data transformations affecting business operations

Do not use for exploratory coding, prototypes, or low-stakes experiments.

Core Workflow

Phase 1: Pre-Execution Planning

Before any code changes, create an execution plan with pre-declared acceptance criteria:

  1. Analyze the request - Identify scope, files, and operations required
  2. Define success criteria - Establish non-negotiable acceptance gates upfront
  3. Select critics - Determine which critic agents are needed (code, security, domain)
  4. Estimate cost - Calculate token overhead (typically +38.6%)
  5. Present plan to user - Show plan with acceptance criteria and get approval

Acceptance criteria must be:

  • Specific and measurable (not "good code" but "all tests pass, coverage >80%")
  • Declared before execution (not emergent)
  • Mapped to critic veto authority (which critic validates which criterion)

Example plan structure:

EXECUTION PLAN

Scope: Refactor authentication to JWT tokens
Files: src/auth/login.ts, src/auth/middleware.ts

SUCCESS CRITERIA (Pre-Declared):
✓ All existing auth tests pass
✓ No OWASP Top 10 vulnerabilities introduced
✓ Token storage uses httpOnly cookies (not localStorage)
✓ Token refresh logic handles 401 responses
✓ Code coverage maintained at 85%+

CRITICS ASSIGNED:
- Code Critic: Test pass rate, coverage, logic correctness
- Security Critic: OWASP compliance, token storage, auth flow
- Domain Critic: Session management business rules

RETRY BUDGET: 6 iterations before escalation
ESTIMATED COST: +40% tokens (~$0.15 additional)

VETO AUTHORITY: ANY critic can reject (unanimous approval required)

Read the full file on GitHub · 416 lines

Files

What ships with it

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

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. 4d ago First seen · 416 lines · 77 tokens per session scan A d5fd959f932c

Subscribe to this mod's changes

Coherence Check is a skill published in the GitHub repository reggiechan74/cc-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 77 tokens to every session and 3,252 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens