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/ilandahan/AIDWrote 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/ilandahan/aid/visual-qa-agent)<a href="https://agentmods.dev/agents/ilandahan/aid/visual-qa-agent"><img src="https://agentmods.dev/badge/agents/ilandahan/aid/visual-qa-agent.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.1 | $0.00043 | $0.03056 |
| Opus 5 | $0.00022 | $0.01528 |
| Sonnet 5 | $0.00009 | $0.00611 |
| Haiku 4.5 | $0.00004 | $0.00306 |
Grade A, and why
visual-qa-agent 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 3d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 3d ago First seen · 347 lines · 43 tokens per session scan A 1435ae1b2f3d
visual-qa-agent is an agent published in the GitHub repository ilandahan/AID (9 stars, last pushed 2d ago), with no licence file. It adds 43 tokens to every session and 3,056 once invoked, about $0.0002 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-04.
Other agents, from other repositories
seo-visual
Visual analyzer. Captures screenshots, tests mobile rendering, and analyzes above-the-fold content using Playwright.
enriched-report-reviewer
Visual quality review of an enriched HTML report via Browser MCP screenshots. Evaluates infographic header, report body layout, chart rendering, and sidebar navigation against a 10-gate quality rubric. Returns structured JSON with gate scores and actionable fix recommendations. Use when enrich-report Phase 5b needs…
UX Designer
UI/UX design specialist with Figma and browser testing expertise.
seo-visual
Visual analyzer. Captures screenshots, tests mobile rendering, and analyzes above-the-fold content using Playwright.
ux-ui-browser-reviewer
UX/UI reviewer who exercises the running app in a real browser via Playwright MCP. Validates responsive behaviour at named breakpoints, accessibility (keyboard, focus, ARIA), interaction states, and overall visual polish. Read-only — does not author code.
ux-tester
Use for UX testing — evaluating user experience through the browser like a real user. Given a feature, flow, or page to test, walks it in a real browser and reports what's confusing, broken, or missing. Doesn't read code or diffs — only sees what the user sees. Triggers: "ux test", "test the ux", "is this confusing"…