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.
git clone --depth 1 https://github.com/ASHR12/irisWrote 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/rules/ashr12/iris/dark-theme-no-banding)<a href="https://agentmods.dev/rules/ashr12/iris/dark-theme-no-banding"><img src="https://agentmods.dev/badge/rules/ashr12/iris/dark-theme-no-banding/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/rules/ashr12/iris/dark-theme-no-banding"><img src="https://agentmods.dev/badge/rules/ashr12/iris/dark-theme-no-banding.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.00000 | $0.00590 |
| Opus 5.5 | $0.00000 | $0.00236 |
| Sonnet 5.5 | $0.00000 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
dark-theme-no-banding 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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dark surfaces must not band
Contour lines in a dark UI come from 8-bit quantization: sRGB has very few code
levels near black, so a wide soft gradient has nothing to put between its steps
and renders as flat plateaus with hard edges. Below the sRGB toe brightness is
proportional to code value, so one step at value 7 is a ~14% brightness jump;
at value 21 it is ~5% and stops reading as a line. Full explanation in
README.md → "Dark UI without colour banding".
Rules
- A gradient that crosses more pixels than it has code levels is not a gradient — it is plateaus with visible edges. Use a flat fill.
- Never take a surface below
--bg-0(#0b111c). Vignettes, scrims and overlays must land above that floor too, or they drag their region back into the crush zone. - Gradients on dark surfaces must be small and steep — a 40px button fade is fine, a 900px wash is not.
- Depth = one step of fill tone + spacing. Not washes, not outlines. Surfaces nest by tone (background → panel → card) and carry no border; borders are only for things that float (menus, popovers).
- One light source. Only the reactor canvas glows. Note the trap: on a flat background a lone soft halo becomes the only brightness variation, which is exactly what vignetting looks like.
/* ❌ BAD — 2 levels of green stretched over 860px, plus window-sized washes */
background:
radial-gradient(92% 78% at 50% 30%, rgba(18, 36, 68, 0.55), transparent 74%),
linear-gradient(180deg, #05070d 0%, #030509 100%);
/* ✅ GOOD */
background: var(--bg-1);
Do not "fix" banding with these
- Noise/dither overlays. Cannot remove a staircase already baked into a
rasterized layer, and
backdrop-filteraverages any dither beneath it away, so banding returns inside blurred glass. mix-blend-mode: overlay. Resolves to2 × backdrop × sourcebelow mid-grey, so on dark surfaces its effect is a fraction of one code level.- More gradient stops. The limit is quantization, not stop count.
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 · 50 lines · 0 tokens per session scan A 149d75a57b3b
dark-theme-no-banding is a cursor rule published in the GitHub repository ASHR12/iris (198 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 590 tokens. 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.
Other cursor rules, from other repositories
explorer-interface-brief
Use when asked to design the interface for an interactive 3D explorer, plan a UI for exploring a 3D model of a topic, or write an image-model prompt for a 3D learning app mock-up. Produces, from a topic, the UI design brief (audience, layout, panels, interactions, label style, colour palette, accessibility) and an…
prototype-previewer
Build interactive prototype reviewers with synced review notes and Figma capture pages.
figma-performance
Handling large documents efficiently in the Plugin API.
ant-design
A set of guidelines for using Ant Design, a collection of ready-made interface components, in React applications. It covers code organization, performance, security, testing, and common mistakes.
7-day-nextjs-web-design-cursor
A seven-day design workflow for web products that will be built in Next.js.
clone-ai
Site Clone AI — website klonlama pipeline kuralları.