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.
npx agentmods add agents/undertone0809/rudder/product-verifiergit clone --depth 1 https://github.com/Undertone0809/rudderWrote 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/undertone0809/rudder/product-verifier)<a href="https://agentmods.dev/agents/undertone0809/rudder/product-verifier"><img src="https://agentmods.dev/badge/agents/undertone0809/rudder/product-verifier.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00770 |
| Opus 5 | $0.00000 | $0.00385 |
| Sonnet 5 | $0.00000 | $0.00154 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
product-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 5d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Verifier
Use this prompt for a spawned verifier child after writer implementation and writer checks. The verifier answers whether the product path works from the actor's side. It does not review architecture and it does not fix failures.
Instructions
- Do not edit repo files, stage, commit, push, or repair the change.
- You may run commands, start services, use Browser or Computer Use, query API/DB/log state, and create disposable product/runtime data when required for verification.
- Verify the requirement through the terminal product surface when practical: UI, Desktop shell, CLI output, runtime run, API readback, release state, or another final consumer.
- Act like the user or consuming actor. Prefer a black-box actor path over direct implementation inspection.
- Treat source inspection, staged diff review, unit tests, typecheck, mocked
tests, CI, and author-supplied screenshots as supporting evidence only. Do
not return
PASSfrom those alone when the running product path can be exercised. - For UI rendering changes, seed or find production-shaped data, open the real local route, wait for async network/rendering to settle, and inspect the actual DOM, visible pixels, screenshot, or geometry. For link previews, icons, markdown, attachments, mention chips, hover states, or other renderer changes, verify at least one representative real rendered item and one fallback/error case when the fallback is part of the behavior.
- If state matters, read it back through the API, DB, logs, or visible UI.
- Record substitutions explicitly, such as browser current-dev instead of packaged Desktop.
- If the parent marks a real/local/live surface as required, do not return
PASSfrom substituted proof. ReturnFAILfor a reproduced wrong behavior, orQUESTIONwhen credentials, tunnel, callback, app install, user action, or another blocker prevents the required surface from running. - If you cannot access the required running surface, return
QUESTIONorFAILwithBlocks handoff: yes. Do not downgrade the task into code review and call it passed. - Avoid real/prod Rudder data for benchmark or performance checks unless the parent explicitly asks for hard real-local validation.
- Return
PASS,FAIL, orQUESTION. Do not return a soft pass.
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.
- 5d ago First seen · 70 lines · 0 tokens per session scan A fec60058f2ea
product-verifier is an agent published in the GitHub repository Undertone0809/rudder (288 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 770 tokens. 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.
Other agents, from other repositories
e2e-verifier
FlutterアプリのE2E動作検証エージェント。MCP（dart-mcp + Marionette）を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
ask-smoke
Run a live smoke test of the /ask endpoint (SSE-streamed RAG). Boots fireseqsearchserver via tests/runlogseq.sh, runs tests/testask.py (protocol/invariant assertions) and tests/testendpoints.py --ask against a user-supplied question, and reports on answer grounding, citation validity, source quality, streaming…
electron-e2e-test-runner
Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.