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 agentmods add instructions/dev-lou/pixelpilot/uiux-testinggit clone --depth 1 https://github.com/dev-lou/PixelPilotWrote 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/instructions/dev-lou/pixelpilot/uiux-testing)<a href="https://agentmods.dev/instructions/dev-lou/pixelpilot/uiux-testing"><img src="https://agentmods.dev/badge/instructions/dev-lou/pixelpilot/uiux-testing.svg" alt="Measured on agentmods" 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.02874 | $0.02874 |
| Opus 5 | $0.01437 | $0.01437 |
| Sonnet 5 | $0.00575 | $0.00575 |
| Haiku 4.5 | $0.00287 | $0.00287 |
Grade A, and why
PixelPilot uiux-testing.instructions.md 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 2d 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 — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI/UX Testing 2026
Testing Trophy, component testing with Storybook, accessibility testing (axe-core), visual regression, and interaction testing for UI/UX systems.
THE TESTING TROPHY (Kent C. Dodds)
/\
/E2E\ ← Few, high-value, slow (Playwright)
/──────\
/Integr. \ ← Most tests live here (React Testing Library)
/──────────\
/ Unit \ ← Small, fast, pure functions/hooks only
/──────────────\
/ Static (types) \ ← TypeScript + ESLint — free tests
/──────────────────\
Ratio target: Static > Unit > Integration > E2E Most value: Integration tests — test behavior, not implementation.
STEP 1 — STATIC ANALYSIS (Free Tests)
// package.json — run before any other test
"scripts": {
"lint": "eslint src --ext .js,.jsx,.ts,.tsx",
"type-check": "tsc --noEmit",
"check": "npm run lint && npm run type-check"
}
// .eslintrc — recommended rules for UI
{
"extends": [
"eslint:recommended",
"plugin:react-hooks/recommended",
"plugin:jsx-a11y/recommended", // catches a11y issues at lint time
"plugin:@typescript-eslint/recommended"
]
}
jsx-a11y catches: missing alt text, bad button usage, unlabeled inputs, missing ARIA. Zero runtime cost. Fix at write time.
STEP 2 — UNIT TESTS (Vitest / Jest)
Only for pure functions — formatters, validators, utils. Not for components.
// lib/format.test.js
import { describe, it, expect } from 'vitest';
import { formatPrice, formatDate, truncate } from './format';
describe('formatPrice', () => {
it('formats USD correctly', () => expect(formatPrice(9.99, 'USD')).toBe('$9.99'));
it('handles zero', () => expect(formatPrice(0, 'USD')).toBe('$0.00'));
it('handles large numbers', () => expect(formatPrice(1234.5)).toBe('$1,234.50'));
});
describe('truncate', () => {
it('truncates long strings', () => expect(truncate('Hello World', 5)).toBe('Hello…'));
it('leaves short strings alone', () => expect(truncate('Hi', 10)).toBe('Hi'));
});
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.
- 2d ago First seen · 370 lines · 2,874 tokens per session scan A c23e7671b72a
PixelPilot uiux-testing.instructions.md is an instructions file published in the GitHub repository dev-lou/PixelPilot (2 stars, last pushed 5mo ago), licensed MIT. It adds 2,874 tokens to every session, about $0.0144 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 instructions, from other repositories
copilot-instructions unit-and-integration-tests.instructions.md
Unit and integration testing best practices with pytest.
instrMCP CLAUDE.md
Claude Code instructions for caidish/instrMCP, covering claude.md, development commands, always use conda environment instrmcpdev for testing, unit tests (fast, no hardware required - all mocked) and e2e tests (requires playwright and browser automation).
Chromanche CLAUDE.md
Claude Code instructions for marcobazzani/Chromanche, covering chromanche — engineering guardrails, testing is non-negotiable, unit tests (vitest), integration tests and red tests block merge.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).