pixelslop: Instructions file for Claude Code

CLAUDE.md

pixelslop CLAUDE.md is an instructions file for Claude Code from gabelul/pixelslop. It costs 4,990 tokens per session, scanned A, original, Apache-2.0.

Project instructions for Pixelslop, a browser-based tool that reviews the visual quality of real web pages using Playwright screenshots and browser-measured styles.

In plain words
What is it for?
Use them when developing, testing, installing, updating, or releasing Pixelslop and its scan, fix, and verification workflow.
Why use it?
They provide the project’s layout, conventions, testing details, and current implementation context so coding agents can make informed changes.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions subagents; mentions Claude Code.

This is gabelul/pixelslop's own configuration. It tells Claude Code how to work on pixelslop itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything pixelslop configures →

Reuse

Borrowing it

Nothing to install: this file belongs to gabelul/pixelslop. 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/gabelul/pixelslop/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/gabelul/pixelslop

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 pixelslop CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/gabelul/pixelslop/claude-md/github.svg)](https://agentmods.dev/instructions/gabelul/pixelslop/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/gabelul/pixelslop/claude-md"><img src="https://agentmods.dev/badge/instructions/gabelul/pixelslop/claude-md/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 pixelslop CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/gabelul/pixelslop/claude-md"><img src="https://agentmods.dev/badge/instructions/gabelul/pixelslop/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 4,990 This file is loaded in full into every session.
When invoked 4,990 The same file — it is already loaded in full.
Security scan A 0 findings. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.04990 $0.04990
Opus 5.5 $0.01996 $0.01996
Sonnet 5.5 $0.00998 $0.00998
Haiku 4.5 $0.00499 $0.00499

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

Security

Grade A, and why

pixelslop CLAUDE.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 2mo 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.

CLAUDE.md · 223 lines

How it starts

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

Pixelslop — Project Conventions

What This Is

Pixelslop is a browser-first design quality reviewer. It opens real pages in Playwright, captures screenshots and computed styles, scores design quality on 5 measurable pillars, and detects AI slop patterns. Browser evidence is the source of truth — no guessing from code.

Current Phase

Phase 5 is complete — updates and distribution. See dev_docs/MASTER-PLAN.md for the full roadmap.

What works now:

  • Installer — npx pixelslop install is interactive by default. It detects Claude Code and Codex CLI, lets the user pick runtimes and scope, supports project-local Codex installs in .codex/, rewrites paths, configures MCP, and installs skills via symlink or copy. npx pixelslop@latest update upgrades the installed runtime set with backup + diff.
  • CI/CD — GitHub Actions for CI (Node 18/20/22) and automated releases via release-please + npm publish with OIDC provenance.
  • Orchestrator — coordinates the full scan→fix→verify workflow. Spawns subagents, manages user interaction, groups findings by category, handles PARTIAL results. Supports --personas and --thorough flags.
  • Scanner — evaluates pages across 3 viewports, scores 5 pillars, detects 26 slop patterns, runs vision-first persona evaluation (the page-relevant subset of 8 built-ins, plus any project persona). Tested on 7 pages, scores stable within ±1.
  • Persona evaluation — 8 built-in personas (screen-reader-user, low-vision-user, keyboard-user, rushed-mobile-user, slow-connection-user, non-native-english, design-critic, first-time-visitor). Extensible JSON format supports custom personas.
  • Fixer — takes a scanner finding, locates the source code, creates a checkpoint via pixelslop-tools, applies the smallest viable fix.
  • Checker — re-measures the targeted metric after a fix, compares before/after, returns PASS/FAIL/PARTIAL. Updates plan via pixelslop-tools.
  • Setup — explores codebase for design context (framework, CSS approach, fonts, tokens), returns structured findings + questions.
  • pixelslop-tools — deterministic CLI for all state management (plan, checkpoints, gates, config, init, verify). Agents call this instead of inline bash. Supports monorepo workspace detection.
  • Checkpoint protocol — file-backup-based fix/verify/rollback mechanism. Both fixer and checker use pixelslop-tools checkpoint *.

Read the full file on GitHub · 223 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.

  1. 2mo ago First seen · 223 lines · 4,990 tokens per session scan A c94f6bbe39cc

Subscribe to this mod's changes

pixelslop CLAUDE.md is an instructions file published in the GitHub repository gabelul/pixelslop (8 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 4,990 tokens to every session, about $0.0200 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-31.

Related

Other instructions, from other repositories

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

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens