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/DataCovey/nornweaveWrote 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/datacovey/nornweave/ui-and-styling-rule)<a href="https://agentmods.dev/rules/datacovey/nornweave/ui-and-styling-rule"><img src="https://agentmods.dev/badge/rules/datacovey/nornweave/ui-and-styling-rule/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/datacovey/nornweave/ui-and-styling-rule"><img src="https://agentmods.dev/badge/rules/datacovey/nornweave/ui-and-styling-rule.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.00068 |
| Opus 5 | $0.00000 | $0.00034 |
| Sonnet 5 | $0.00000 | $0.00014 |
| Haiku 4.5 | $0.00000 | $0.00007 |
Grade A, and why
ui-and-styling-rule 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 9d 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
- Utilize Tailwind CSS utility classes for styling components.
- Follow Shadcn UI component guidelines and best practices.
- Ensure UI is responsive and accessible.
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.
- 9d ago First seen · 10 lines · 0 tokens per session scan A 71e701b6a051
ui-and-styling-rule is a cursor rule published in the GitHub repository DataCovey/nornweave (27 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 68 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
design
All tasks related to updating frontend components, CSS, and general styling.
antd-design-system
A maintenance guide for interfaces built with Ant Design, a React component library, and antd-style, its styling companion. The description only says it applies to existing components.
figma-shadcn-ui-generate
1:1 Figma design implementation using shadcn/ui, Tailwind CSS, and React. Apply when implementing or converting Figma designs to code, building UI from design specs, or when user mentions Figma URLs or design-to-code.
color-tokens
A rule set for choosing interface colors through shared semantic design tokens. These tokens are named meanings such as primary, success, notice, or destructive rather than fixed color values.
shadcn-tailwind-guide
A guide to building new components with shadcn/ui and Tailwind CSS, a utility-based system for styling interfaces.
mobile-responsive
A set of rules for making interfaces adapt to phones and other screen sizes. Responsive design changes layout and sizing so a site remains usable on different devices.