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 lfyxhappy/lfcode --skill visual-regression-testergit clone --depth 1 https://github.com/lfyxhappy/lfcodeWrote 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/lfyxhappy/lfcode/visual-regression-tester)<a href="https://agentmods.dev/skills/lfyxhappy/lfcode/visual-regression-tester"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/visual-regression-tester/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/lfyxhappy/lfcode/visual-regression-tester"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/visual-regression-tester.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.00371 |
| Opus 5.5 | $0.00023 | $0.00148 |
| Sonnet 5.5 | $0.00011 | $0.00074 |
| Haiku 4.5 | $0.00006 | $0.00037 |
Grade A, and why
visual-regression-tester 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
Visual Regression Tester
Compare rendered output with deliberate baselines rather than relying on source inspection.
Workflow
- Read repository instructions, design requirements, existing screenshot tests, baseline ownership rules, and the actual rendered artifact to inspect.
- Define comparable states: viewport or device, scale factor, color scheme, locale, fonts, browser or runtime version, data fixture, navigation state, and loading readiness.
- Capture a baseline only from a verified intended state. Use stable test data and wait for meaningful content and fonts rather than fixed delays.
- Capture the candidate through the same path, then inspect the visual diff and relevant DOM, console, network, or accessibility evidence when pixels alone are ambiguous.
- Classify differences as intended product change, layout or styling defect, missing asset, rendering-environment variance, or unstable test setup.
- Update a baseline only after confirming the rendering change is intentional and reviewing the full affected surface, then rerun the focused visual check.
Boundaries
- Keep visual assessment read-only unless the user asks to change tests, baselines, or product code.
- Do not approve or regenerate baselines merely to make a visual test pass.
- Do not compare screenshots with uncontrolled fonts, network data, animations, time, locale, or viewport conditions.
- Do not expose customer content, access tokens, or sensitive screenshots in reports or committed artifacts.
Completion Check
Report the compared artifact, controlled rendering conditions, baseline decision, inspected differences, verification command, and any remaining platform variance.
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 First seen · 29 lines · 57 tokens per session scan A c569a02f9dfe
visual-regression-tester is a skill published in the GitHub repository lfyxhappy/lfcode (2 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 371 once invoked, about $0.0002 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-09-05.
Other skills, from other repositories
performance-engineer
Becomes a senior performance engineer who identifies bottlenecks, designs optimization strategies, and conducts load testing using systematic profiling and benchmarking methodology. Use when the user needs performance analysis, load testing, bottleneck identification, latency optimization, or capacity planning. Do NOT…
Check work (verify against criteria)
Verify an implementation against acceptance criteria with a reviewer and a tester.
PR babysit (watch & drive to green)
Watch a pull request and delegate fixes until CI is green and reviews are addressed. Requires the GitHub MCP server or gh.
Write tests
Add focused, meaningful tests for code — happy path plus the edge cases that matter.
playwright
Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via playwright-cli or the bundled wrapper script.
develop-web-game
Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with rendergametotext.