dark-mode-testing

dark-mode-testing is a skill for Claude Code from spencerpauly/awesome-cursor-skills. It costs 28 tokens per session (531 once invoked), scanned A, original, CC0-1.0.

A procedure for checking that a website works in both light mode and dark mode. It uses screenshots and the browser's page structure to find visual problems such as unreadable text, missing borders, or bright flashes.

In plain words
What is it for?
Use it to test a page in light and dark themes, compare the two states, and identify colors or borders that need dark-theme alternatives.
Why use it?
It catches theme problems that may be missed when testing only one color scheme. This helps prevent pages that look broken or are difficult to read in dark mode.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Good fit Use it to test a page in light and dark themes, compare the two states, and identify colors or borders that need dark-theme alternatives.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/spencerpauly/awesome-cursor-skills/dark-mode-testing
Install

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.

Any agent
npx skills add spencerpauly/awesome-cursor-skills --skill dark-mode-testing
Clone the repo
git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills

Made for: Claude Code.

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.

agentmods badge for dark-mode-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/spencerpauly/awesome-cursor-skills/dark-mode-testing/github.svg)](https://agentmods.dev/skills/spencerpauly/awesome-cursor-skills/dark-mode-testing)
Your own site
<a href="https://agentmods.dev/skills/spencerpauly/awesome-cursor-skills/dark-mode-testing"><img src="https://agentmods.dev/badge/skills/spencerpauly/awesome-cursor-skills/dark-mode-testing/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.

agentmods 80×15 button for dark-mode-testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/spencerpauly/awesome-cursor-skills/dark-mode-testing"><img src="https://agentmods.dev/badge/skills/spencerpauly/awesome-cursor-skills/dark-mode-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 531 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
  • Socket pass 14 Sept 2026
  • Snyk pass 14 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00531
Opus 5.5 $0.00011 $0.00212
Sonnet 5.5 $0.00006 $0.00106
Haiku 4.5 $0.00003 $0.00053

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

Security

Grade A, and why

dark-mode-testing 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

resources/dark-mode-testing/SKILL.md · 65 lines

What it actually says

Dark Mode Testing

Verify that dark mode works correctly by toggling themes and comparing.

Workflow

1. Open the App

Navigate to the target page using browser_navigate.

2. Screenshot Light Mode

Take a screenshot of the page in its default (light) state using browser_take_screenshot.

3. Toggle Dark Mode

Toggle dark mode using one of these methods (try in order):

  1. Class toggle: Execute JS to add dark class to <html>:
    document.documentElement.classList.toggle('dark')
    
  2. Attribute toggle: Set data-theme="dark":
    document.documentElement.setAttribute('data-theme', 'dark')
    
  3. Media query: Use browser to emulate prefers-color-scheme: dark
  4. UI toggle: Find the theme toggle button in browser_snapshot and click it

4. Screenshot Dark Mode

Take another screenshot after toggling.

5. Inspect for Issues

Check the browser_snapshot aria tree and screenshots for:

  • White flashes: Elements with hardcoded bg-white instead of bg-white dark:bg-slate-900
  • Invisible text: Text color that matches the dark background (e.g. black text on dark bg)
  • Missing borders: Borders using light-only colors that disappear on dark backgrounds
  • Contrast violations: Text that's too low-contrast against the dark background (need 4.5:1)
  • Hardcoded colors: Any #ffffff, #000000, white, black in inline styles
  • Images: Logos or icons that don't have dark mode variants
  • Shadows: Box shadows that are invisible on dark backgrounds
  • Form inputs: Input fields that keep white backgrounds in dark mode

6. Report

Dark Mode Test:
  Light mode: OK
  Dark mode issues found:
    - Header logo: white logo invisible on dark bg (needs dark variant)
    - Card borders: border-gray-200 invisible on dark bg → add dark:border-gray-700
    - Footer text: hardcoded #333 → use text-gray-900 dark:text-gray-100

Fix each issue and re-test.

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.

  1. 1mo ago First seen · 65 lines · 28 tokens per session scan A c38f390931bd

Subscribe to this mod's changes

dark-mode-testing is a skill published in the GitHub repository spencerpauly/awesome-cursor-skills (864 stars, last pushed 2mo ago), licensed CC0-1.0. It adds 28 tokens to every session and 531 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-30.

Related

Other skills, from other repositories

eval-dataset-design

A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.

bojieli/ai-agent-book · 138 tokens

verify-omnigent

Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…

omnigent-ai/omnigent · 100 tokens

test-master

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…

Jeffallan/claude-skills · 104 tokens

dogfood

Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.

callstack/agent-device · 55 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

critique

Adversarial design critique of the current work — render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.

plugin87/ux-ui-agent-skills · 37 tokens