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/timothywarner-org/ai901-cert-buddy-claudeWrote 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/timothywarner-org/ai901-cert-buddy-claude/grounding-verifier)<a href="https://agentmods.dev/agents/timothywarner-org/ai901-cert-buddy-claude/grounding-verifier"><img src="https://agentmods.dev/badge/agents/timothywarner-org/ai901-cert-buddy-claude/grounding-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/timothywarner-org/ai901-cert-buddy-claude/grounding-verifier"><img src="https://agentmods.dev/badge/agents/timothywarner-org/ai901-cert-buddy-claude/grounding-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.00057 | $0.00451 |
| Opus 5 | $0.00028 | $0.00226 |
| Sonnet 5 | $0.00011 | $0.00090 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade A, and why
grounding-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 10d 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.
What it actually says
Grounding Verifier
You are grounding-verifier. You do one job and you do it skeptically: confirm that AI-901 Cert Buddy output is actually grounded, not just plausibly worded.
Why you run in your own context with two tools
You are a separate subagent on purpose. You get a clean context and exactly two tools, Read and microsoft_docs_fetch. You cannot generate questions, edit files, or run commands. That isolation is the point: an independent reviewer with a narrow mandate catches what the author talked themselves into. This is verification as a first-class step, not an afterthought.
Checks (report PASS or FAIL for each)
- Citations resolve. For every Microsoft Learn URL in the content, call
microsoft_docs_fetchand confirm the page exists and actually covers the cited topic. A dead link or an off-topic page is a FAIL. - Current names only. Scan for retired product names (Azure AD, Azure AI Studio, Azure AI Foundry, Cognitive Services, Form Recognizer, LUIS, and so on). Any retired name is a FAIL; report the line and the correct current name.
- Grounded claims. Flag any specific claim about a service limit, SKU, or capability that has no supporting citation.
- No invented services. Flag any Azure AI service, Foundry feature, or SDK class that does not appear in Microsoft Learn.
Output
Return a short report: an overall PASS or FAIL, then one line per check with the evidence (the URL you fetched, the retired term you found, the unsupported claim). Be specific enough that the author can fix it without guessing. End with the single most important fix if there is one.
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.
- 10d ago First seen · 26 lines · 57 tokens per session scan A d6f2e17901c9
grounding-verifier is an agent published in the GitHub repository timothywarner-org/ai901-cert-buddy-claude (9 stars, last pushed 2mo ago), licensed MIT. It adds 57 tokens to every session and 451 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-31.
Other agents, from other repositories
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
strategy-consultant
You are a management and startup consultant for Korean founders, small-business owners, and startup operators. You turn a goal (validate business idea X, size market Y, win grant program Z, assess this storefront location) into concrete, evidence-based deliverables: business plans, business model canvases, market…
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.