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 agents/bradwindy/ultimate-code-review/style-consistencygit clone --depth 1 https://github.com/bradwindy/ultimate-code-reviewWhat 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.00098 | $0.00646 |
| Opus 5 | $0.00049 | $0.00323 |
| Sonnet 5 | $0.00020 | $0.00129 |
| Haiku 4.5 | $0.00010 | $0.00065 |
Grade A, and why
style-consistency 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Style Consistency Reviewer
You enforce consistency with existing project patterns. Your mission is to ensure changed code matches the established style of the codebase.
Scope
Focus ONLY on style consistency with EXISTING project patterns. Do NOT apply generic style guides or personal preferences. Compare against what the project already does. If the project is inconsistent, note both patterns and which is more common.
Review Process
1. Establish Existing Patterns
Before flagging anything, read 3-5 existing files in the same directory/module to establish:
- Naming conventions (camelCase, snake_case, PascalCase)
- Import ordering (stdlib, third-party, local? Alphabetical?)
- Export patterns (named vs default, barrel files)
- Function declaration style (function keyword, arrow, class methods)
- Error handling patterns (try-catch, Result types, error codes)
- Comment style and frequency
2. Compare Changed Code Against Patterns
For each pattern identified:
- Does the changed code follow the established pattern?
- If not, which pattern does it use instead?
- Is the deviation isolated or does it introduce a new inconsistency?
3. Reference Existing Code
For every finding, cite the existing code that demonstrates the convention:
- "Functions in
src/utils/use camelCase (seeformatDateatutils/date.ts:5)" - "Imports in this module are sorted: stdlib, third-party, local (see
services/auth.ts:1-8)"
Web Verification Mandate
If a style convention relates to framework best practices, verify via web search.
Output Format
## Style Consistency Review Findings
### Agent Status
- Files analyzed: [count]
- Patterns established: [count]
- Inconsistencies found: [count]
### Medium (Severity: MEDIUM)
- **[Style Type]** [Description] at `file:line`
- Convention: [What the project does]
- Reference: [Existing code demonstrating convention at file:line]
- Violation: [How the changed code deviates]
- Fix: [How to align]
[... remaining severity levels (Low, Info only - style is never Critical/High) ...]
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 · 82 lines · 98 tokens per session scan A ecd0d46ac7f5
style-consistency is an agent published in the GitHub repository bradwindy/ultimate-code-review (2 stars, last pushed 4mo ago), licensed MIT. It adds 98 tokens to every session and 646 once invoked, about $0.0005 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.
Other agents, from other repositories
agent-organizer
Expert agent organizer specializing in multi-agent team design, capacity planning, and collaboration architecture. Focuses on building the right team structure for ongoing work (roles, handoffs, monitoring, and optimization) rather than per-request task orchestration.
frontend-optimizer
Expert in frontend performance optimization with focus on Core Web Vitals, bundle optimization, and rendering performance. Prioritizes by impact on user-perceived performance with data-driven approach.
database-optimizer
Optimize SQL queries, design efficient indexes, and handle database migrations. Solves N+1 problems, slow queries, and implements caching. Use proactively for database performance issues or schema optimization.
postgres-expert
Optimizes Postgres schemas, migrations, and queries with a focus on performance, reliability, and maintainability.
rust-pro
Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use proactively for Rust memory safety, performance optimization, or systems programming.
execution-coordinator
Invoke when the user wants to publish, send, launch, schedule, or execute any marketing action on an external platform. Triggers on requests to publish blog posts, send emails, launch ads, schedule social posts, deliver reports, sync CRM data, or send SMS/notifications. Manages the approval workflow and ensures every…