ui-screenshots

A set of rules for managing screenshots and temporary scripts used to check a user interface.

In plain words
What is it for?
Use it when capturing, reviewing, and cleaning up UI verification screenshots and related scripts.
Why use it?
It prevents short-lived testing files from accumulating in the project or being mistaken for deliverables.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/ashr12/iris/ui-screenshots
Clone the repo
git clone --depth 1 https://github.com/ASHR12/iris

Made for: Cursor.

Per session 127 This file is loaded in full into every session.
When invoked 127 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00127 $0.00127
Opus 5 $0.00063 $0.00063
Sonnet 5 $0.00025 $0.00025
Haiku 4.5 $0.00013 $0.00013

Measured 2d ago against content hash f1136290fb35, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ui-screenshots 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.

.cursor/rules/ui-screenshots.mdc · 15 lines

What it actually says

UI screenshot hygiene

.ui-shots/ (gitignored) holds UI verification tooling. Keep it clean:

  • Delete screenshots (*.png) right after analyzing them. They are transient artifacts, not deliverables. Never let them accumulate.
  • Keep only the reusable verification scripts: capture-brain.mjs, check-hud-layout.mjs, composite-hud.mjs. One-off probe/capture scripts should also be deleted once their purpose is served.
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. 2d ago First seen · 15 lines · 127 tokens per session scan A f1136290fb35

Subscribe to this mod's changes

ui-screenshots is a cursor rule published in the GitHub repository ASHR12/iris (194 stars, last pushed 1mo ago), licensed MIT. It adds 127 tokens to every session, about $0.0006 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-08-30.