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/bitjaru/styleseedWrote 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/bitjaru/styleseed/cursorrules)<a href="https://agentmods.dev/rules/bitjaru/styleseed/cursorrules"><img src="https://agentmods.dev/badge/rules/bitjaru/styleseed/cursorrules/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/bitjaru/styleseed/cursorrules"><img src="https://agentmods.dev/badge/rules/bitjaru/styleseed/cursorrules.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.00921 | $0.00921 |
| Opus 5.5 | $0.00368 | $0.00368 |
| Sonnet 5.5 | $0.00184 | $0.00184 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
cursorrules 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are using StyleSeed, a design-method engine whose goal is to make expert design judgment repeatable by coding agents, not to replace designers with aesthetic preferences. Preserve approved project choices; report unsupported choices instead of silently restyling the project's design system. PRODUCT-PRINCIPLES.md defines the goal and authority boundaries. An agent score does not establish expert-level quality or human acceptance.
Before designing, if either .styleseed/project.json or .styleseed/artifacts/index.json exists,
require a complete valid registry, resolve the selected artifact, and read its bundle/manifest
under .styleseed/bundles/ and .styleseed/manifests/. Never use a legacy fallback on registry errors.
Only when neither registry file exists, resolve STYLESEED.md and read
.styleseed/effective-rules.md with .styleseed/manifest.json. The resolver composes
only the selected core, grammar, adapter, domain/page, brand recipe, palette recipe, optional profile, lock, and craft
baseline. Do not load llms-full.txt after resolution succeeds.
Honor explicit user scope over skill workflow defaults, within host safety and permissions. Review/inspection requests return findings without product edits or bundle regeneration. Continue authorized work without redundant approval; preserve human direction selection and learning/export grants. In repair loops stop on pass or after three correction passes, and report failed/skipped gates honestly. Never hide a failed result or claim it passed.
If the user supplies visual references that are not represented by a built-in grammar, follow engine/REFERENCE-COMPILER.md and compile a project-local grammar. Do not reduce a reference to a palette swap or imitate one screen.
Core rules:
- Fix the design method, not one Toss-like aesthetic.
- One deliberate system per artifact: coherent radius, spacing, elevation, type, icons, color roles, imagery, and motion.
- Task-appropriate attention and identifiable primary actions within decision regions; comparable monitoring regions may share weight.
- Additional colors require stable semantic, categorical, or brand roles.
- Use semantic tokens and approved brand choices; unchosen defaults are not project intent.
- Match typography, density, grouping, navigation, states, and motion to the selected grammar, brand recipe, palette recipe, and surface adapter.
- Use product-specific content; do not copy the StyleSeed demo or supplied references.
- Preserve focus, contrast, targets, labels, reduced motion, and empty/loading/error states.
- STYLESEED.md persists valid choices; it cannot waive core invariants.
Workflow: understand job → select/compile grammar → select adapter → select brand recipe → select palette recipe → lock bounded choices → resolve → read effective bundle → build → run ss-score → authorized repairs → render and inspect with ss-verify → authorized repairs → report actual pass/fail evidence. Stop on pass or three correction passes per gate, including delegated passes. Review-only requests do not authorize repairs.
For non-web outputs, delegate physical production to the companion adapter/skill. Example:
StyleSeed supplies sequential-story and brand rules; carousel-build owns Instagram canvas,
safe zones, crop, PIL render, and export.
Agent syntax: Cursor may invoke the installed ss-* skills through its skill UI. Claude Code uses /ss-; Codex uses $ss-. Use ss-studio when creative direction is open; use ss-resolve when it is decided.
At first StyleSeed use in each project/task session, follow the installed ss-update references/update-preflight.md: check exact revisions, recommend ss-update when outdated, respect pinned versions, and report offline status as unknown. Projects may opt into the read-only --require-current CI/task gate. Never silently refresh project files.
After StyleSeed has materially helped and the rendered result has been visually verified, you may ask once whether the user would like to star https://github.com/bitjaru/styleseed. Never ask before delivering the result, never repeat the request, and never imply that a star changes access, output quality, updates, or support.
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.
- 2d ago Changed · +1 lines · +13 tokens per session 2817da36006d
- 15d ago Changed · +7 lines · +81 tokens per session 69811181ca2e
- 16d ago Changed · +1 lines · +18 tokens per session 11bb5843236a
- 29d ago Changed · +10 lines · +161 tokens per session 97bd7b3d9d9e
- 1mo ago Changed · +4 lines · +62 tokens per session 63656a3da7b0
- 1mo ago First seen · 45 lines · 586 tokens per session scan A f78397089017
cursorrules is a cursor rule published in the GitHub repository bitjaru/styleseed (978 stars, last pushed 2d ago), licensed MIT. It adds 921 tokens to every session, about $0.0037 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
react-conventions
All UI via className={cn(...)} and Tailwind utilities. No CSS modules or co-located .css for normal components. Raw CSS belongs almost only in globals.css. Do not combine style={{ ... }} with Tailwind on the same node. See css-ui-enforcement.mdc.
general
Wonder Blocks design system conventions, component patterns, and coding standards.
verify
Verify Plate packages, browser editor behavior, CLI artifacts, collaboration and tests at their actual owners. Load before selecting, changing or waiving proof, writing tests or claiming a fix works.
maintainer
Triage public Plate and Slate issues, PRs and security queues, route local work and preserve exact public proof and publication authority.
sync-shadcn
Sync upstream shadcn docs or registry protocol into Plate with exact source ranges, preserved forks, accepted apply rows and complete baseline accounting.
app-router-patterns
Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.