finding-checker

finding-checker is an agent for Claude Code from hypnguyen1209/offensive-claude. It costs 52 tokens per session (1,030 once invoked), scanned A, original, MIT.

A deliberately context-limited reviewer for checking written findings and the evidence files they cite. It tries to disprove the finding using only those materials, without seeing the author's reasoning.

In plain words
What is it for?
Use it in a bounded review loop to challenge security or other investigative findings and return a structured rebuttal when the evidence is insufficient.
Why use it?
It can expose unsupported claims, missing evidence, or evidence that does not actually prove the stated conclusion.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the offensive-claude plugin — 30 skills, 18 commands, 8 agents, 1 hook shipped together

Good fit Use it in a bounded review loop to challenge security or other investigative findings and return a structured rebuttal when the evidence is insufficient.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/hypnguyen1209/offensive-claude/finding-checker
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.

Clone the repo
git clone --depth 1 https://github.com/hypnguyen1209/offensive-claude

Made for: Claude Code.

Or install offensive-claude, the plugin that ships this one along with the rest of its 30 skills, 18 commands, 8 agents, 1 hook.

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 finding-checker

README.md
[![agentmods](https://agentmods.dev/badge/agents/hypnguyen1209/offensive-claude/finding-checker.svg)](https://agentmods.dev/agents/hypnguyen1209/offensive-claude/finding-checker)
Your own site
<a href="https://agentmods.dev/agents/hypnguyen1209/offensive-claude/finding-checker"><img src="https://agentmods.dev/badge/agents/hypnguyen1209/offensive-claude/finding-checker.svg" alt="Measured on agentmods" height="20"></a>
Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,030 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00052 $0.01030
Opus 5 $0.00026 $0.00515
Sonnet 5 $0.00010 $0.00206
Haiku 4.5 $0.00005 $0.00103

Measured 8d ago against content hash 6b5f60c1144a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

finding-checker 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 8d 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.

agents/finding-checker.md · 68 lines

How it starts

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

You are a blind finding checker. You are deliberately given ONLY the written finding and the evidence files it cites — never the author's reasoning, chat, or context. Your job is to decide whether the claim follows from the artifact alone. A finding that only makes sense if you already trust the author is not proven.

You are not the same role as finding-validator. The validator is the pipeline judge with full context that issues PASS/KILL/DOWNGRADE. You are the second, context-starved reviewer whose structured rebuttal feeds the bounded rebuttal loop (engine/rebuttal.py): generator asserts → you try to refute → if you can't, it is ACCEPTED; if you keep refuting the same way it STALLS; if rounds run out it is EXHAUSTED (downgraded, never auto-accepted). Default to refuting when unsure.

What you do (only from the artifact)

  1. Open every cited evidence file and [EVD-XXX] item yourself. If a claim has no backing artifact on disk, that is a refutation (missing_evidence). Do not infer the artifact exists.
  2. Check the evidence shows what the claim says — not merely something adjacent. An SSRF claim needs the internal response in the file, not a 200; an RCE needs command output, not a hang. Use skills/references/finding-evidence-standards.md as the per-class bar.
  3. Run the mechanical gates and read their output as inputs, not as proof of honesty:
    • validate_findings.py --findings f.json --evidence ./evidence --evidence-store evidence.json --strict
    • evidence_kit.py verify --store evidence.json (any non-VERIFIED cited item is a refutation)
  4. Flag ungrounded language. Hedges ("probably", "should work", "likely exploitable") and any leap the evidence does not support are refutations, not style notes.
  5. Do not invent corroboration. If you can't open an artifact, that is a refutation, not a guess.

Output (structured, one object)

{"refuted": true,
 "reasons": ["evidence/F1.txt shows a 302 to a same-origin path, not an external host"],
 "missing_evidence": ["no response body for the IMDS claim"],
 "hedges": ["'should be exploitable'"],
 "uncited_claims": ["privilege escalation asserted with no EVD reference"],
 "confidence": "AMBIGUOUS",
 "rubric_version": "1.0.0"}

Read the full file on GitHub · 68 lines

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. 8d ago First seen · 68 lines · 52 tokens per session scan A 6b5f60c1144a

Subscribe to this mod's changes

finding-checker is an agent published in the GitHub repository hypnguyen1209/offensive-claude (357 stars, last pushed 21d ago), licensed MIT. It adds 52 tokens to every session and 1,030 once invoked, about $0.0003 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-30.

Related

Other agents, from other repositories

bt6-pr-auditor

Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.

elder-plinius/T3MP3ST · 32 tokens

parallel-reviewer

Parallel code review using 4 specialist agents (elixir-reviewer, security-analyzer, testing-reviewer, verification-runner). Use for thorough review of significant changes.

oliver-kriska/claude-elixir-phoenix · 38 tokens

codex-reviewer

Run OpenAI Codex CLI code review and normalize findings into review panel format. Use when /phx:review runs with --codex for a cross-model second opinion on Elixir/Phoenix changes. Requires codex CLI; degrades to SKIPPED note.

oliver-kriska/claude-elixir-phoenix · 60 tokens

project-auditor

Use for /audit or when no PROJECT.md exists. Auditor + Architect hybrid — stack detection, vulnerability analysis, outdated dependency scan, architectural debt, and a concrete refactoring plan.

avelikiy/great_cto · 41 tokens

legal-reviewer

Legal-services / legal-tech specialist pre-implementation reviewer for legal archetype (law firms, solo practitioners, legal-SaaS). Outputs threat model TM-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.

avelikiy/great_cto · 52 tokens

accounting-reviewer

Bookkeeping / general-ledger / financial-close specialist pre-implementation reviewer for fintech and enterprise-saas archetypes. Outputs threat model TM-accounting-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.

avelikiy/great_cto · 52 tokens