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/jaycewalzer1/SilverKey-Inc.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.
[](https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./responsive-ui)<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./responsive-ui"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./responsive-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/jaycewalzer1/silverkey-inc./responsive-ui"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./responsive-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.00000 | $0.00564 |
| Opus 5.5 | $0.00000 | $0.00226 |
| Sonnet 5.5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
responsive-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.
What it actually says
Responsive UI (SilverKey)
Canonical reference: documentation/guides/responsive-ui-standards.md — read it for WEB-1–WEB-8, RN-1–RN-10, BOTH-1–BOTH-5, SilverKey route notes, and the seven-area path map.
Must follow (summary)
- Mobile-first (web): Base layout for small screens; add
sm:/md:/lg:only to enhance. Do not usemax-widthhacks to bolt mobile onto desktop-first layouts. - No accidental desktop changes: Preserve desktop appearance unless fixing a real bug or applying a necessary global rule. Prefer minimal diffs.
- Overflow: Use
min-w-0on flex children with long text; wrap tables inoverflow-x-auto. Do not addoverflow-x-hiddento ancestors ofposition: stickywithout checking sticky behavior. - Touch targets: ≥44×44px (web: min size / padding; RN:
minHeight/minWidthorhitSlop). - Forms (web): Inputs use at least
text-baseon touch devices to reduce iOS zoom-on-focus. - React Native:
SafeAreaViewfromreact-native-safe-area-contexton root screens; keyboard +ScrollViewpatterns per doc; bounded images (width: '100%'+aspectRatiowhere appropriate). - Design system: Keep using standardized
Button,Title,BodyText, etc. fromClient/packages/ui/(or@/components/ui/@uialiases) — responsive work adjusts layout and primitives, not one-off raw<button>/heading styles.
SilverKey specifics
- Public landing lives under
packages/features/homeauth/.../landing/(webHomeFeature.web.tsx). - Post-login (web): default is
/dashboard, not a separate home route. - Mobile auth welcome:
HomeScreenNativeis pre-login; first tab after auth is Dashboard.
After edits
Run pnpm lint and pnpm typecheck in Client/ when touching responsive code (see documentation/reference/linting.md).
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 · 33 lines · 0 tokens per session scan A e44cd8170c00
responsive-ui is a cursor rule published in the GitHub repository jaycewalzer1/SilverKey-Inc. (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 564 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
css-styling
CSS architecture, tokens, and styling rules for this Docusaurus site. Apply when creating or modifying components, styles, layouts, or any UI-facing code.
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.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
z-index
Z-index layering conventions for consistent stacking.
shadcn-tailwind-guide
A guide to building new components with shadcn/ui and Tailwind CSS, a utility-based system for styling interfaces.