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/romkey/I2C-DirectoryWrote 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/romkey/i2c-directory/ui)<a href="https://agentmods.dev/rules/romkey/i2c-directory/ui"><img src="https://agentmods.dev/badge/rules/romkey/i2c-directory/ui/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/romkey/i2c-directory/ui"><img src="https://agentmods.dev/badge/rules/romkey/i2c-directory/ui.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.02175 | $0.02175 |
| Opus 5.5 | $0.00870 | $0.00870 |
| Sonnet 5.5 | $0.00435 | $0.00435 |
| Haiku 4.5 | $0.00217 | $0.00217 |
Grade A, and why
ui 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Design Rules
Apply these rules to any HTML/template/CSS Cursor writes for this project. The system uses Bootstrap 5.3 with data-bs-theme="dark" and a custom refresh.css that defines the component classes referenced below.
Core principles
-
Color encodes meaning, not category. Reserve color for: red = danger/destructive, amber = warning/needs attention, green = success/active, blue = active/selected/link. Never color-code categories of buttons (e.g., don't make "all parking buttons green"). If color isn't telling the user something specific, it shouldn't be there.
-
Dim the common case so outliers pop. When 90%+ of values in a column are identical (statuses, amounts, dates), render the common case in muted gray and let exceptions stand out.
-
One primary action per region. At most one filled
btn-primaryper page region. Everything else isbtn-outline-secondary. -
Pages should do work, not just present data. Surface attention counts inline. Make filters surface admin problems. Lead with what the user can act on.
-
Density beats whitespace. This is an admin tool. Body text is 12-13px in tables. Tighten padding aggressively.
Buttons
btn-primary— single most-used action per region only.btn-outline-secondary— everything else.btn-danger/btn-outline-danger— only for genuinely destructive actions (Delete, Ban, Remove). Destructive buttons go in a⋯kebab menu, never bare on the page.- Never use
btn-success/btn-warning/btn-infoas button color labels for categories. Use semantic meaning only.
Status indicators
- 90%+ rows share a status → render a 6px colored dot (
.status-dot.status-successetc.), no label. - Exceptional statuses → use a small
text-bg-*-subtlebadge with a label. - Never use saturated
bg-success/bg-dangerfilled badges. Always use the-subtlevariants. - ALL CAPS status pills are forbidden. Sentence case only.
Numbers and money
- Right-align numeric columns with
class="num"(tabular). - Zero values:
text-secondary(muted). - Outlier values in a column of similar values: add
fw-medium. - Money: dim repeated parts.
<span class="money num"><span class="currency">$</span>40<span class="cents">.00</span></span>— only the dollar value is bright. - Never wrap counts in colored badges (e.g.,
<span class="badge bg-info">42</span>). Plain numerals.
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 · 174 lines · 2,175 tokens per session scan A 4317e41c99da
ui is a cursor rule published in the GitHub repository romkey/I2C-Directory (11 stars, last pushed 11d ago), licensed MIT. It adds 2,175 tokens to every session, about $0.0087 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-30.
Other cursor rules, from other repositories
external-scale
Source: docs/agents/external-scale.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
mobile-first-ui
Mobile-first UI for settings, dialogs, and lists — smaller type, stacked layouts, nested add dialogs.
ui-motion-workflow
Orchestrate motion-aware UI work by sequencing direction, provider choice, implementation, and browser validation.
frontend-design-direction
Derive a brief-specific visual direction, token sketch, hierarchy, and signature element.