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/ashishpatill/tell-proofWrote 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/ashishpatill/tell-proof/tell-ui-design)<a href="https://agentmods.dev/rules/ashishpatill/tell-proof/tell-ui-design"><img src="https://agentmods.dev/badge/rules/ashishpatill/tell-proof/tell-ui-design.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.00000 | $0.00248 |
| Opus 5 | $0.00000 | $0.00124 |
| Sonnet 5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
tell-ui-design 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 8d 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.
What it actually says
Tell UI rules
Follow docs/01_DESIGN_SYSTEM.md. Dogfood: Tell must not trigger its own tells.
- Fonts: Instrument Serif + Source Sans 3 + IBM Plex Mono — never Inter-only
- No violet gradient hero, no shadow on every card
- Use semantic Tailwind tokens:
bg-surface,text-secondary,text-accent - Raw hex belongs in
globals.csstokens only, not TSX classNames - Full state matrix on interactive components: hover, focus-visible, active, disabled, loading/error where applicable
- Preserve the signature
BeforeAfterSeam; keyboard and reduced-motion behavior are part of the feature - Copy from USER_STORY.md copy bank — critic voice, no emoji chrome
- Hero = Tell Report + reveal seam, not KPI dashboard
- Current UI is mostly
apps/web/src/app/page.tsx; extract components only when it reduces real complexity
Use @ui-builder (Composer) for components; @ux-copywriter (GPT 5.5) for copy polish.
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.
- 8d ago First seen · 22 lines · 0 tokens per session scan A 2f6632c940fe
tell-ui-design is a cursor rule published in the GitHub repository ashishpatill/tell-proof (1 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 248 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-31.
Other cursor rules, from other repositories
cis-design-thinking-maestro
CIS Agent — Maya (Design Thinking Maestro).
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
agents
Always-loaded project anchor. Read this first. Contains project identity, non-negotiables, commands, and pointer to ROUTER.md for full context.
researcher
Researcher agent.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.