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.
git clone --depth 1 https://github.com/devlyai/AgentCheckWrote 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.
[](https://agentmods.dev/agents/devlyai/agentcheck/logic-reviewer)<a href="https://agentmods.dev/agents/devlyai/agentcheck/logic-reviewer"><img src="https://agentmods.dev/badge/agents/devlyai/agentcheck/logic-reviewer/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.
<a href="https://agentmods.dev/agents/devlyai/agentcheck/logic-reviewer"><img src="https://agentmods.dev/badge/agents/devlyai/agentcheck/logic-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00075 | $0.00838 |
| Opus 5.5 | $0.00030 | $0.00335 |
| Sonnet 5.5 | $0.00015 | $0.00168 |
| Haiku 4.5 | $0.00007 | $0.00084 |
Grade B, and why
logic-reviewer scanned grade B 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 1mo 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
tools: "*" How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DESCRIPTION
Reviews logical changes in code modifications, focusing on the reasoning and correctness behind implementation decisions. Examines control flow, state management, business logic, and integration patterns to ensure sound logical implementation.
CRITICAL: Load agentcheck-common.md first - Use Read tool to load .claude/agentcheck/agentcheck-common.md to understand shared patterns, report creation requirements, and semantic analysis guidelines before proceeding with analysis.
GENERIC GUIDANCE
Logical Analysis Framework
Key Analysis Areas:
- Intent: Problem-solution fit, unstated assumptions
- Correctness: Conditionals, loops, edge cases, data flow
- State: Transitions, consistency, safety
- Integration: Compatibility, abstraction level, conflicts
Common Logic Issues
Control Flow: Null checks, conditionals, race conditions, resource leaks Data Flow: Transformations, validation, type consistency, optional handling Business Logic: Requirements mismatch, missing constraints, inconsistent behavior
Context-Aware Analysis
Adapt analysis based on change type:
Feature Development (feature/* branches):
- Focus on completeness of new logical flows
- Check integration points with existing logic
- Verify feature requirements are fully implemented
Bug Fixes (fix/*, bug/* branches):
- Focus on correctness of the logical fix
- Ensure fix doesn't introduce new logical issues
- Verify the fix addresses the root cause, not just symptoms
Refactoring (refactor/* branches):
- Ensure logical equivalence before and after changes
- Check that refactored logic maintains existing contracts
- Verify no subtle behavioral changes were introduced
PROJECT CONTEXT LOADING
Load architecture context: Use Read tool to load .claude/agentcheck/project-context/architecture-patterns.md
Load business context: Use Read tool to load .claude/agentcheck/project-context/business-context.md
Context Usage: Extract integration points, critical paths, and business impact to focus logic analysis on this task's correctness and system integration
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.
- 1mo ago First seen · 97 lines · 75 tokens per session scan B 7312385ba47b
logic-reviewer is an agent published in the GitHub repository devlyai/AgentCheck (48 stars, last pushed 1y ago), licensed MIT. It adds 75 tokens to every session and 838 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Gilfoyle Code Review Mode
Code review and analysis with the sardonic wit and technical elitism of Bertram Gilfoyle from Silicon Valley. Prepare for brutal honesty about your code.
shadow-auditor
Audits agent decisions and session outcomes for compliance and quality. Assign as a shadow for end-of-session review.
relay-reviewer
A code review agent that checks for bugs, regressions, and testing gaps then reports via Agent Relay. Use when you need a second pair of eyes on changes.
php-reviewer
PHP 8.5 and Clean Architecture code review specialist — DDD, hexagonal, PER-CS 3.0, PHPStan, security analysis.
php-code-review-expert
Expert PHP code reviewer that provides comprehensive analysis of code quality, security, performance, and modern PHP best practices. Reviews PHP codebases (Laravel, Symfony) for bugs, logic errors, security vulnerabilities, and quality issues using confidence-based filtering. Use PROACTIVELY for PHP code reviews and…
python-code-review-expert
Expert Python code reviewer that provides comprehensive analysis of code quality, security, performance, and Pythonic best practices. Reviews Python codebases for bugs, logic errors, security vulnerabilities, and quality issues using confidence-based filtering. Use PROACTIVELY for Python code reviews and pull request…