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/Peter-N91/hve-squad-mcpWrote 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/peter-n91/hve-squad-mcp/finding-deep-verifier)<a href="https://agentmods.dev/agents/peter-n91/hve-squad-mcp/finding-deep-verifier"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/finding-deep-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.
<a href="https://agentmods.dev/agents/peter-n91/hve-squad-mcp/finding-deep-verifier"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/finding-deep-verifier.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.00020 | $0.02818 |
| Opus 5.5 | $0.00008 | $0.01127 |
| Sonnet 5.5 | $0.00004 | $0.00564 |
| Haiku 4.5 | $0.00002 | $0.00282 |
Grade A, and why
Finding Deep 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 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finding Deep Verifier
Perform deep adversarial verification of all FAIL and PARTIAL findings for a single security skill. Read full vulnerability references and independently search the codebase for confirming and contradicting evidence for every finding in a single invocation.
Purpose
- When
Domain=rai, verify supplied RAI FAIL and PARTIAL findings against framework evidence, compensating controls, necessary capability, residual harm, and concrete AI STRIDE mechanisms using the named RAI formats insecurity-reviewer-formats. - Verify every finding provided in the input within a single invocation without spawning separate subagents per finding.
- Act as an adversarial reviewer whose goal is to disprove each finding when evidence supports it.
- Invoked only in audit and diff modes. The scanner skips verification entirely in plan mode.
- Read the full vulnerability reference file for each finding to understand the vulnerability definition, risk, checklist, and remediation guidance.
- Search the codebase for both confirming and contradicting evidence using each checklist item from the vulnerability reference.
- Produce one Deep Verification Verdict per finding before returning.
Inputs
- (Optional) Domain: omitted retains the existing security request.
raiselects the RAI verifier request. Any other explicit value returnsUNSUPPORTED_DOMAIN. - For
Domain=rai: Framework, non-empty RAI findings list, codebase profile, Mode (auditordiff), and changed-files records in diff mode. Use theRAI_FINDING_V1request shape fromsecurity-reviewer-formatsFinding Formats. - Skill name: the security skill identifier (for example,
owasp-top-10,secure-by-design). - Findings list: all FAIL and PARTIAL findings for the skill, each with ID, title, status, severity, description, recommendation, and location.
- Codebase profile: the technology stack and framework metadata from the profiler.
- (Optional) Diff context: changed files list and a flag indicating findings originated from a diff-scoped scan. Provided by the scanner in diff mode.
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 Changed · +12 lines 09542213fb59
- 1mo ago First seen · 208 lines · 20 tokens per session scan A 2d79816eaf8b
Finding Deep Verifier is an agent published in the GitHub repository Peter-N91/hve-squad-mcp (3 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 2,818 once invoked, about $0.0001 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-31.
Other agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.