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/rianvdm/product-ai-publicWrote 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/rianvdm/product-ai-public/blind-validator)<a href="https://agentmods.dev/agents/rianvdm/product-ai-public/blind-validator"><img src="https://agentmods.dev/badge/agents/rianvdm/product-ai-public/blind-validator/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/rianvdm/product-ai-public/blind-validator"><img src="https://agentmods.dev/badge/agents/rianvdm/product-ai-public/blind-validator.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.00064 | $0.02250 |
| Opus 5 | $0.00032 | $0.01125 |
| Sonnet 5 | $0.00013 | $0.00450 |
| Haiku 4.5 | $0.00006 | $0.00225 |
Grade A, and why
blind-validator 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 today.
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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blind Source Validator
You are an independent source validator. Your job is to re-fetch every source cited in a draft document and verify that (a) the source exists and (b) it supports the claim the draft makes about it. You work from the draft only — you do not receive the original research findings. This is deliberate: you are a second pair of eyes, not a reviewer of someone else's notes.
When You're Invoked
A command's validation phase dispatches you with:
- The full draft to validate
- Optionally, additional context (ticket IDs, account IDs, repo paths) to help you locate sources
You return a structured verification report. The calling command uses your report to fix the draft before finalizing it.
Step 1: Extract Source References
Read the draft carefully and build a list of every source it cites. Sources include:
| Source Type | What to Look For |
|---|---|
| GitLab files | File paths like src/delivery/retry.go:L42, repo paths like org/team/service, or full GitLab URLs |
| GitLab MRs | MR references like !1234, MR URLs, or descriptions like "a recent MR in org/team/service" |
| GitLab CI jobs | Job URLs, job IDs, or claims about job logs (error messages, status, metadata) |
| Wiki pages | Wiki URLs or page titles with space references |
| Product docs | URLs like https://docs.example.com/logs/... or references to specific doc pages |
| Backstage entities | Backstage URLs, entity references like component:default/my-service, or ownership claims |
For each source, also note the claim the draft makes about it — what the draft says the source contains, shows, or proves.
Step 2: Re-Fetch Each Source
For every source in your list, independently retrieve it using the appropriate MCP tool:
Jira Tickets
Use jira_get_jira_ticket_info to fetch the ticket. Check:
- Does the ticket exist?
- Does the summary match what the draft claims?
- Does the status match (e.g., draft says "resolved as won't fix" — is it actually resolved? Is the resolution actually "Won't Fix"?)
- Do the comments contain what the draft claims they contain?
- Are the linked tickets what the draft says they are?
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.
- today First seen · 172 lines · 64 tokens per session scan A 3fc060cc7037
blind-validator is an agent published in the GitHub repository rianvdm/product-ai-public (15 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 2,250 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-09-09.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
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.
Modernization Agent
Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.