What is update-screenshots?

A procedure for replacing component screenshot baselines with screenshots produced by the latest GitHub Actions run, GitHub's automated build and test service.

Use it when screenshot tests report visual differences or when you need to accept or refresh their baselines. It requires the GitHub CLI to be signed in and a screenshot-diff artifact from a completed workflow run.

Screenshots can differ between a developer's computer and the Linux system used by continuous integration. Using the CI result keeps the approved baseline consistent with the test environment.

How malwarebo/nyrve configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to malwarebo/nyrve. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/malwarebo/nyrve/main/.github/skills/update-screenshots/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/malwarebo/nyrve

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/malwarebo/nyrve/update-screenshots/github.svg)](https://agentmods.dev/skills/malwarebo/nyrve/update-screenshots)

Your own site

<a href="https://agentmods.dev/skills/malwarebo/nyrve/update-screenshots"><img src="https://agentmods.dev/badge/skills/malwarebo/nyrve/update-screenshots/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/malwarebo/nyrve/update-screenshots"><img src="https://agentmods.dev/badge/skills/malwarebo/nyrve/update-screenshots.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 832 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00056	$0.00832
Opus 5.5	$0.00022	$0.00333
Sonnet 5.5	$0.00011	$0.00166
Haiku 4.5	$0.00006	$0.00083

Measured 1mo ago against content hash 1eb983bfdf90, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

update-screenshots scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf test/componentFixtures/.screenshots/baseline/

.github/skills/update-screenshots/SKILL.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Update Component Screenshots from CI

When asked to update, accept, or refresh screenshot baselines from CI — or when the Screenshot Tests GitHub Action has failed with screenshot differences — follow this procedure to download the CI-generated screenshots and commit them as the new baselines.

Why CI Screenshots?

Screenshots captured locally may differ from CI due to platform differences (fonts, rendering, DPI). The CI (Linux, ubuntu-latest) is the source of truth. This skill downloads the CI-produced screenshots and commits them as baselines.

Prerequisites

The gh CLI must be authenticated (gh auth status).
The Screenshot Tests GitHub Action must have run and produced a screenshot-diff artifact.

Procedure

1. Find the latest screenshot artifact

If the user provides a specific run ID or PR number, use that. Otherwise, find the latest run:

# For a specific PR:
gh run list --workflow screenshot-test.yml --branch <branch> --limit 5 --json databaseId,status,conclusion,headBranch

# For the current branch:
gh run list --workflow screenshot-test.yml --branch $(git branch --show-current) --limit 5 --json databaseId,status,conclusion

Pick the most recent run that has a screenshot-diff artifact (runs where screenshots matched won't have one).

2. Download the artifact

gh run download <run-id> --name screenshot-diff --dir .tmp/screenshot-diff

The artifact is uploaded from two paths (test/componentFixtures/.screenshots/current/ and test/componentFixtures/.screenshots/report/), but GitHub Actions strips the common prefix. So the downloaded structure is:

current/ — the CI-captured screenshots (e.g. current/baseUI/Buttons/Dark.png)
report/report.json — structured diff report
report/report.md — human-readable diff report

3. Review the changes

Show the user what changed by reading the markdown report:

cat .tmp/screenshot-diff/report/report.md

4. Copy CI screenshots to baseline

Read the full file on GitHub · 97 lines

Changes

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 · 97 lines · 56 tokens per session scan C 1eb983bfdf90

Subscribe to this mod's changes

update-screenshots is a skill published in the GitHub repository malwarebo/nyrve (5 stars, last pushed 4mo ago), licensed MIT. It adds 56 tokens to every session and 832 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code E2E testing Testing ai-agents ide

mirrord-chaos

Help users chaos test their app with mirrord: inject artificial latency or connection errors into a mirrord session's outgoing traffic via per-session chaos rules managed with the mirrord chaos CLI. Use when a user wants to add latency or delay to outgoing connections or a dependency (e.g. a slow database), simulate…

metalbear-co/mirrord · 119 tokens

verify-bb

Verify BB user journeys in an isolated source dev app using dev-browser@next and the matching source CLI. Use after BB feature changes or when asked to verify or smoke-test BB. The feature map covers core UI and agent interfaces, every repository plugin, desktop, mobile, and hosted services; select the affected…

get-bb/bb · 70 tokens

create-verification-skill

Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".

get-bb/bb · 57 tokens

maintain-verification-skill

Audit an existing verification skill and feature map against source and the running app, then repair proven documentation or harness drift. Use for "maintain the verification skill", "audit the verify skill", or "refresh the verification feature map".

get-bb/bb · 53 tokens

mirrord-ci

Help users set up mirrord in CI pipelines for testing against real Kubernetes environments. Use when users want to run end-to-end tests, integration tests, or automated tests in CI using mirrord to connect to staging/shared clusters.

metalbear-co/mirrord · 52 tokens

bug-bash

Run an agent bug bash of the Xum web UI in the bug-bash sandbox (TesterArmy e2e explore charters, each in its own locked-down Docker container with a seeded xum server), then verify each finding with a failing repro test. Use when asked to "bug bash" Xum, run e2e explore agents, the MCP Apps suite or the story tests…

coder/xum · 100 tokens

nyrve: Skill for Claude Code