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 Nolane-x/forge-os --skill reviewing-visual-regressionsgit clone --depth 1 https://github.com/Nolane-x/forge-osWrote 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/nolane-x/forge-os/reviewing-visual-regressions)<a href="https://agentmods.dev/skills/nolane-x/forge-os/reviewing-visual-regressions"><img src="https://agentmods.dev/badge/skills/nolane-x/forge-os/reviewing-visual-regressions/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/nolane-x/forge-os/reviewing-visual-regressions"><img src="https://agentmods.dev/badge/skills/nolane-x/forge-os/reviewing-visual-regressions.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.00041 | $0.01477 |
| Opus 5 | $0.00020 | $0.00739 |
| Sonnet 5 | $0.00008 | $0.00295 |
| Haiku 4.5 | $0.00004 | $0.00148 |
Grade A, and why
reviewing-visual-regressions 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 7d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewing Visual Regressions
Overview
This skill owns one bounded responsibility: reviewing visual regressions. Its focus is reviewing visual regressions within ux lifecycle boundaries. It converts declared inputs into typed artifacts and reproducible evidence without silently changing product scope.
Trigger
Activate only when the project is in one of these stages: ux-design, all contract preconditions pass, and the router identifies a missing output this skill can produce. Do not activate merely because the skill name resembles the user request.
Required Inputs
product-definitionuser-workflows- Current gate result, open findings, artifact hashes, and invalidation state
- Required tools: none
- Optional tools:
browser - Confirmed human decisions relevant to this scope
Method-Specific Protocol
- Define the exact decision, actors, objects, states, invariants, side effects, and non-goals owned by reviewing visual regressions.
- Build a decision table for normal, boundary, invalid, permission, failure, retry, recovery, concurrency, migration, and abuse conditions relevant to reviewing visual regressions.
- Apply reviewing visual regressions only to direct input artifacts; record assumptions, rejected alternatives, and any human decision still required.
- Trace the resulting contract to user value, security, reliability, cost, operability, and downstream consumers.
- Create reproducible checks that would fail if reviewing visual regressions were incomplete or implemented incorrectly.
Procedure
- Read user workflows, constraints, devices, and accessibility needs.
- Define critical journeys and failure recovery before visual styling.
- Define the exact decision, actors, objects, states, invariants, side effects, and non-goals owned by reviewing visual regressions.
- Build a decision table for normal, boundary, invalid, permission, failure, retry, recovery, concurrency, migration, and abuse conditions relevant to reviewing visual regressions.
- Apply reviewing visual regressions only to direct input artifacts; record assumptions, rejected alternatives, and any human decision still required.
- Trace the resulting contract to user value, security, reliability, cost, operability, and downstream consumers.
- Create reproducible checks that would fail if reviewing visual regressions were incomplete or implemented incorrectly.
- Specify interaction states, information hierarchy, and feedback.
- Create responsive and accessible behavior contracts.
- Validate critical flows against realistic user tasks.
- Publish UI evidence, open questions, and handoff contracts.
What ships with it
1 file 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.
- 7d ago First seen · 134 lines · 41 tokens per session scan A 133b1d9277af
reviewing-visual-regressions is a skill published in the GitHub repository Nolane-x/forge-os (10 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 1,477 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-03.
Other skills, from other repositories
cli-command
Design, implement, or review Composio CLI commands under ts/packages/cli using Effect, @effect/cli, services, output conventions, configuration and environment variables, and local vendor references. Use for CLI command UX, command wiring, service changes, or CLI source edits. Do not use for CLI E2E-only work; use…
ui-craft-checks
Use this comprehensive gate for formal review, QA, launch handoff, exact-fidelity inspection, high-risk complex UI, or when the fast gate exposes a deeper craft problem. Ordinary single-screen work uses ui-design-executor and its bundled validator without loading this full matrix. Pair standalone artifacts with…
ui-testing
Visual testing - catch invisible buttons, broken layouts, contrast.
visual-validation
Autonomous screenshot verification — captures, compares, and AI-evaluates UI changes for visual regressions.
qa
Run scalable, isolated live QA for nac development. The top-level local orchestrator must parse n (default 4), dispatch one setup worker with this skill, copy its n assignment contracts verbatim into exactly n parallel test workers with this skill, then dispatch one aggregate worker with this skill using all test…
app-user-story-qa
End-to-end app feature inventory and user-story testing workflow with a canonical tracker. Use when the user asks to audit every feature, derive expected behavior from code, test user journeys, or explicitly fix and retest documented UX or logistical defects.