finding-verifier

finding-verifier is an agent for Claude Code from animalzinc/claude-plugins. It costs 46 tokens per session (423 once invoked), scanned A, original, MIT.

A second reviewer that checks another reviewer's findings against the exact style rule and surrounding lines. It keeps, changes, or removes each finding.

In plain words
What is it for?
Use it after style, usage, voice, or structure reviews to validate findings and correct proposed replacements.
Why use it?
Reviewers can flag text that a rule does not cover, miss an exception, or suggest an unsafe correction. Independent verification reduces those incorrect findings.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter.

Part of the blog-style-guide-creator plugin — 4 skills, 2 commands, 11 agents shipped together

Good fit Use it after style, usage, voice, or structure reviews to validate findings and correct proposed replacements.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/animalzinc/claude-plugins/finding-verifier
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/animalzinc/claude-plugins

Made for: Claude Code.

Or install blog-style-guide-creator, the plugin that ships this one along with the rest of its 4 skills, 2 commands, 11 agents.

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-verifier

README.md
[![agentmods](https://agentmods.dev/badge/agents/animalzinc/claude-plugins/finding-verifier/github.svg)](https://agentmods.dev/agents/animalzinc/claude-plugins/finding-verifier)
Your own site
<a href="https://agentmods.dev/agents/animalzinc/claude-plugins/finding-verifier"><img src="https://agentmods.dev/badge/agents/animalzinc/claude-plugins/finding-verifier/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.

agentmods 80×15 button for finding-verifier

Your own site · 80×15
<a href="https://agentmods.dev/agents/animalzinc/claude-plugins/finding-verifier"><img src="https://agentmods.dev/badge/agents/animalzinc/claude-plugins/finding-verifier.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 423 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.00046 $0.00423
Opus 5.5 $0.00018 $0.00169
Sonnet 5.5 $0.00009 $0.00085
Haiku 4.5 $0.00005 $0.00042

Measured 2d ago against content hash 9d2c4cf46a7b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

finding-verifier 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.

plugins/blog-style-guide-creator/agents/finding-verifier.md · 29 lines

What it actually says

You are the second reader. Another reviewer flagged passages in an article; you decide which flags hold. The style-check skill gives you a verifier packet path.

Input

<run>/verify/<pass>.md holds, for each finding: its ID, the rule's text exactly as the guide states it (with severity and exceptions), the article lines around the passage (two above and two below), the quoted passage, and the reviewer's proposed replacement or comment.

Task

For each finding, decide from the rule text and the passage alone, not from the reviewer's reasoning:

  • keep: the rule, as written, covers this exact passage, no exception in the rule applies, and the replacement (if any) fixes it without breaking the sentence.
  • revise: the rule applies, but the replacement is wrong (it changes meaning, breaks grammar, or fixes more than the problem). Give a corrected replacement of exactly the quoted span.
  • drop: the rule does not cover the passage, an exception applies, the passage is quoted speech, the flag rests on a preference the rule does not state, or the finding duplicates another one in the packet.

Brand guides often depart from common style advice on purpose. Judge by what this guide says, never by what you would recommend.

Output

Write <run>/verify/<pass>.verdicts.json: a JSON array with one object per finding: {"id": "F0007", "verdict": "keep", "reason": "<one line>"}, adding "replacement": "<text>" for revise. Every finding in the packet gets a verdict. Reply with the counts of keep, revise, and drop and the file path only.

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. 2d ago First seen · 29 lines · 46 tokens per session scan A 9d2c4cf46a7b

Subscribe to this mod's changes

finding-verifier is an agent published in the GitHub repository animalzinc/claude-plugins (15 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 423 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-11-11.

Related

finding-verifier compared with agents from other repositories

finding-verifier next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
finding-verifieranimalzinc/claude-pluginsAgent152d agoMITA46Claude Code
seo-geo-optimizerteachskillofskills-ai/ContentForge-techshuAgent12mo agoMITA29Claude Code
researcherteachskillofskills-ai/ContentForge-techshuAgent12mo agoMITA26Claude Code
fact-checkerteachskillofskills-ai/ContentForge-techshuAgent12mo agoMITA24Claude Code
content-drafterteachskillofskills-ai/ContentForge-techshuAgent12mo agoMITA22Claude Code
structurer-proofreaderteachskillofskills-ai/ContentForge-techshuAgent12mo agoMITA24Claude Code
batch-orchestratorteachskillofskills-ai/ContentForge-techshuAgent12mo agoMITA25Claude Code