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 skills add AkshitIreddy/agent-skills --skill visual-verificationgit clone --depth 1 https://github.com/AkshitIreddy/agent-skillsWrote 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/skills/akshitireddy/agent-skills/visual-verification)<a href="https://agentmods.dev/skills/akshitireddy/agent-skills/visual-verification"><img src="https://agentmods.dev/badge/skills/akshitireddy/agent-skills/visual-verification/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/skills/akshitireddy/agent-skills/visual-verification"><img src="https://agentmods.dev/badge/skills/akshitireddy/agent-skills/visual-verification.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.00023 | $0.00348 |
| Opus 5.5 | $0.00009 | $0.00139 |
| Sonnet 5.5 | $0.00005 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
visual-verification 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.
What it actually says
Verify the rendered result
Render the affected product surface, capture it, and open the image at readable scale before claiming a visual outcome. A passing build or an unopened screenshot does not establish appearance. Use the project's existing harness when possible.
Choose the relevant evidence
- For a component change, inspect that component and its affected states.
- For a whole-screen audit, inspect overlapping readable close-ups covering the screen before judging the full composition. Open each close-up, record what it shows, then inspect the next. A contact sheet is useful for routing, not a substitute for detail inspection. Recapture affected regions after corrections.
- For web interactions, read browser QA.
- For transient motion defects, read motion evidence.
- If a capture harness is needed, see capture examples.
Inspect presence, clipping, alignment, legibility, contrast, and visual hierarchy. Cover the viewport sizes and empty, loading, error, ready, focus, or disabled states relevant to the change. Keep a narrow fix from becoming an unrelated audit.
A specimen board supports an asset or direction decision. Inspect the integrated surface and affected controls before calling the feature complete. Distinguish headless, development, packaged-app, and device evidence in the report.
Run required checks and relevant verification. After they pass, broaden or repeat only for a new change, failure, or unresolved concern. If rendering is unavailable, continue useful work and state the verification gap plainly.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · -83 lines · -50 tokens per session af403daca645
- 1mo ago First seen · 117 lines · 73 tokens per session scan A 8d8ae0a12546
visual-verification is a skill published in the GitHub repository AkshitIreddy/agent-skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 348 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 skills, from other repositories
lov-maintain-partners
Maintain the Skill Publisher website's partners section AND align partner logo rows on event posters / hero strips: reuse lov-find-logo for brand logo discovery, normalize collected logos to a 240px-tall content canvas (retina-ready), rasterize SVGs via rsvg-convert before normalizing (so SVG viewBox padding gets…
lov-oh-my-landingpage
A landing-page creation and redesign skill that derives a product’s positioning, story, and visual direction from its actual product and brand facts. It then implements the page responsively and checks the result against the intended product message.
lov-frontend-design
A frontend design guide for turning requirements, existing screens, and real media into usable pages and components. It covers visual design, navigation, interaction details, animation, images, audio, and video.
lov-install-shadcn-ui
A setup tool for shadcn/ui, a collection of editable interface components for web projects. It installs only needed pieces and adapts their styles to the project’s existing theme and Tailwind version.
lov-install-web-logo
A website branding tool that connects an approved logo to browser icons, the web app manifest, page metadata, and related components. A favicon is the small icon shown in a browser tab; a PWA manifest describes an installable web app.
lov-kill-emoji
A UI cleanup tool that replaces unsuitable emoji in visible interface elements with matching icons or short text. It checks the surrounding meaning before changing anything.