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.
npx agentmods add rules/bitjaru/styleseed/cursorrulesgit clone --depth 1 https://github.com/bitjaru/styleseedWhat 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 | $0.00586 | $0.00586 |
| Opus 5 | $0.00293 | $0.00293 |
| Sonnet 5 | $0.00117 | $0.00117 |
| Haiku 4.5 | $0.00059 | $0.00059 |
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 yesterday.
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
You are using StyleSeed, an AI design-method engine for product UI and other visual artifacts.
Before designing, invoke the installed ss-resolve skill from STYLESEED.md, then read
.styleseed/effective-rules.md and preserve .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.
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.
- One focal point and one identifiable primary action.
- Additional colors require stable semantic, categorical, or brand roles.
- Use semantic tokens; avoid accidental pure black and generic default indigo.
- 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 to >=80 → render and inspect with ss-verify → fix and re-render → present evidence.
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.
On first StyleSeed use per project, you may compare the local engine/VERSION with https://styleseed-demo.vercel.app/version.json. Mention ss-update once only when a newer version exists; never block work or nag.
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.
- yesterday First seen · 45 lines · 586 tokens per session scan A f78397089017
cursorrules is a cursor rule published in the GitHub repository bitjaru/styleseed (928 stars, last pushed 6d ago), licensed MIT. It adds 586 tokens to every session, about $0.0029 per session on Opus 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
mdc-files
Best practices for writing .mdc cursor rules files.
slate-plan
Review Slate v2 architecture/API plans against React 19.2 runtime performance, Slate-close unopinionated DX, legacy-regression proof, research evidence, and shadcn-style composability; write a scored plan and keep completion pending until every required pass and closure gate is complete.
sync-shadcn
Autogoal-backed planning, status, review, dashboard, apply, and tracking for upstream shadcn docs syncs into Plate docs. Use when the user asks for sync-shadcn, sync-shadcn status, sync-shadcn review, sync-shadcn dashboard, sync-shadcn apply, a scoped sync-shadcn lane, to sync shadcn docs, audit newer shadcn docs…
plate-plan
Define or update Plate editor-behavior specs with a pass-gated, evidence-scored plan. Use for behavior law, authority maps, protocol rows, parity gates, research-backed winner shifts, editor chrome contracts, and implementation-roadmap changes.
clawsweeper
Triage and process the Slate v2 issue ledger with OpenClaw-style sweep discipline: archive-first discovery, duplicate proof, small-fix gates, exact claim rules, maintainer-safe issue output, and gitcrawl API refreshes.
editor-test-harvester
Mine external editor repositories for portable editor-behavior tests with ClawSweeper-style discipline: multi-pass exhaustive inventory, confidence scoring, framework-specific skip reasons, Slate/Plate coverage mapping, license-aware invariant extraction, and copy/refactor/create decisions.