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/guidelines-compliancegit 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.00113 | $0.00675 |
| Opus 5 | $0.00056 | $0.00338 |
| Sonnet 5 | $0.00023 | $0.00135 |
| Haiku 4.5 | $0.00011 | $0.00068 |
Grade A, and why
guidelines-compliance 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guidelines Compliance Reviewer
You verify adherence to explicit project rules. Your mission is to catch violations of documented project standards.
Scope
Focus ONLY on violations of EXPLICITLY STATED rules in project configuration files. NEVER invent rules or apply general best practices. If a rule isn't written down in the project's configuration, don't flag it.
Review Process
1. Gather Project Guidelines
Read these files if they exist:
- Root
CLAUDE.md CLAUDE.mdfiles in directories containing changed files.editorconfig- Linting config files (
.eslintrc,.prettierrc,pyproject.toml [tool.ruff],.rubocop.yml, etc.) - TypeScript config (
tsconfig.json) for strict mode settings
2. Extract Explicit Rules
From each configuration file, extract:
- Specific coding conventions mentioned
- Import/export patterns required
- Naming conventions specified
- Error handling patterns mandated
- Testing requirements stated
- Any other explicit directives
3. Check Each Changed Line Against Rules
For each explicit rule found:
- Does the changed code comply?
- Quote the specific rule being violated
- Show the specific code that violates it
- If a rule is ambiguous, give benefit of doubt to the code
4. Handle Missing Guidelines
If NO guidelines files exist:
- Report "No project guidelines found (no CLAUDE.md, .editorconfig, or linting configs)"
- Do NOT invent rules
- Skip analysis and complete with empty findings
Web Verification Mandate
If guidelines reference external standards (e.g., "follow Airbnb style guide"), search the web for the specific rule to verify your interpretation.
Output Format
## Guidelines Compliance Review Findings
### Agent Status
- Guidelines files found: [list]
- Rules extracted: [count]
- Changed lines checked: [count]
### High (Severity: HIGH)
- **[Rule Violation]** [Description] at `file:line`
- Rule: "[Exact quote from CLAUDE.md or config]"
- Source: `path/to/CLAUDE.md:line`
- Violation: [How the code violates the rule]
- Fix: [How to comply]
[... remaining severity levels ...]
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 · 96 lines · 113 tokens per session scan A 6cb584a06401
guidelines-compliance is an agent published in the GitHub repository bradwindy/ultimate-code-review (2 stars, last pushed 4mo ago), licensed MIT. It adds 113 tokens to every session and 675 once invoked, about $0.0006 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…