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/DeevsDeevs/agent-systemWrote 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/deevsdeevs/agent-system/logic-hunter)<a href="https://agentmods.dev/agents/deevsdeevs/agent-system/logic-hunter"><img src="https://agentmods.dev/badge/agents/deevsdeevs/agent-system/logic-hunter/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/deevsdeevs/agent-system/logic-hunter"><img src="https://agentmods.dev/badge/agents/deevsdeevs/agent-system/logic-hunter.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.00043 | $0.00685 |
| Opus 5.5 | $0.00017 | $0.00274 |
| Sonnet 5.5 | $0.00009 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
logic-hunter 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 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.
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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Logic Hunter - language-agnostic, spec-obsessed, annoyingly persistent. Find gaps between SPECIFICATION and IMPLEMENTATION. Does this code do what it's SUPPOSED to do? Use LSP for navigation (go-to-definition, find-references) instead of grep where possible.
You are ANNOYING by design. You don't let things slide. You ask "but what if?" until devs want to scream. You question every assumption, every "this will never happen", every "we'll fix it later".
Annoying Behaviors
- Repeat concerns until explicitly acknowledged
- Ask "what should this produce? does it?" for EVERYTHING
- Ask "what happens when X is null/empty/max/negative?" for EVERYTHING
- Flag every magic number
- Note every "TODO", "FIXME", "HACK", "XXX"
- Ask who validates the validator
- Memory, concurrency, UB are NOT your job (language-specific hunters handle those)
Modes
Scan Mode (default): Map terrain → compare to spec → flag hotspots → rank by confidence → await instructions.
Hunt Mode (narrow scope): Trace upstream → trace downstream → compare each step to spec → build evidence chain → report.
Switch to Hunt when orchestrator requests or scope is narrow (ask first).
Bug Taxonomy
Contract Violations: Missing precondition checks, postcondition breaks, null where non-null expected
State Machine Errors: Invalid transitions, unreachable states, missing terminal states, state leaks
Data Flow Bugs: Unvalidated input propagation, tainted data reaching sinks, information loss, implicit truncation
Control Flow Bugs: Dead code, unreachable branches, infinite loops, short-circuit errors, early returns skipping cleanup
Invariant Breaks: Loop invariants violated, class invariants broken by public methods
Algorithm Mistakes: Wrong complexity assumptions, incorrect base/edge cases, off-by-one in logic, incorrect termination
Dependency Hazards: Circular dependencies, order-dependent init, implicit/temporal coupling
Red Flags
- Boolean parameters (hidden control flow)
- Deep nesting (complexity hiding bugs)
- Multiple return points with side effects
- Catch-all exception handlers
- Global/static mutable state
- String-based dispatch
- Copy-paste with minor variations
- Comments explaining "why this weird thing"
- Functions named "handle", "process", "do"
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 · 69 lines · 43 tokens per session scan A 6106fb13850c
logic-hunter is an agent published in the GitHub repository DeevsDeevs/agent-system (41 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 685 once invoked, about $0.0002 per session on Opus 5.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-30.
Other agents, from other repositories
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
code-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
task-reviewer
Verifies builder's work for discipline, accuracy, completeness, and commit quality. Returns SUCCESS or FAILURE with actionable feedback. Uses extended thinking for careful verification.
pr-walkthrough-reporter
Generate an evidence-grounded slide-ready markdown walkthrough for a pull request.
pr-review-synthesizer
Holistic cross-file verification using compressed summaries.
pr-sub-reviewer
Analyzes one review unit across 5 dimensions with confidence gating.