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 skills/bitjaru/styleseed/ss-restylenpx skills add bitjaru/styleseed --skill ss-restylegit 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/skills/bitjaru/styleseed/ss-restyle)<a href="https://agentmods.dev/skills/bitjaru/styleseed/ss-restyle"><img src="https://agentmods.dev/badge/skills/bitjaru/styleseed/ss-restyle.svg" alt="Measured on agentmods" 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 | $0.00026 | $0.00499 |
| Opus 5 | $0.00013 | $0.00249 |
| Sonnet 5 | $0.00005 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
ss-restyle 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 4d 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
Apply an aesthetic profile
Registry-first artifact boundary
When .styleseed/project.json and .styleseed/artifacts/index.json exist, resolve the requested artifact ID first, then read only .styleseed/bundles/<artifact-id>.md and .styleseed/manifests/<artifact-id>.json. Never fall back to the global legacy bundle for a registry project. Legacy projects may use .styleseed/effective-rules.md only when no registry exists.
Read PRODUCT-PRINCIPLES.md, RULESETS.md, PRESETS.md, and STYLESEED.md. Profiles are
coordinated visual axes; output grammars organize attention, information, and action. Keep them
separate.
Workflow
- Validate that the lock has one output grammar. If not, run
/ss-setupfirst. - Select exactly one profile from
PRESETS.md, ornone. Never stack profiles. - Apply its coordinated radius, density, type, palette temperature, elevation, motion, composition accent, and signature move inside the output grammar's allowed ranges.
- Preserve deliberate brand values and required fonts when compatible. If incompatible, the output grammar and core invariants win; explain the conflict.
- Update
Aesthetic profileand affected bounded values inSTYLESEED.md. Do not rewrite the output grammar or a reference-compiled rule set. - Run
/ss-scoreto ≥80 and/ss-verifyif renderable. Report the complete effective rule set, not just the profile name.
Rules
- A profile is optional appearance coordination, not a design-method exemption.
technicalprofile does not turn a commerce page into an observability console.editorialprofile does not justify unreadable serif body in a transaction workflow.brutalist-litestill requires coherent states, contrast, and one border language.- Use
/ss-dialfor one-axis changes and/ss-referencefor a new evidence-derived language.
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.
- 4d ago First seen · 37 lines · 26 tokens per session scan A fa451824b42a
ss-restyle is a skill published in the GitHub repository bitjaru/styleseed (939 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 499 once invoked, about $0.0001 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 skills, from other repositories
sigil-migration
Before migrating, audit the existing project.
sigil-component
Every Sigil component lives in packages/components/src/ and follows this pattern.
elite-engineer
The operating system for elite software engineering in TypeScript, React, and Next.js. Enforces the cognitive models, architecture laws, type-level patterns, component design, visual standards, and performance mandates that separate exceptional software from the ordinary — grounded in named sources (Torvalds…
design-to-code
Lanhu to Code workflow for Claude Code. Convert Lanhu design URLs into Vue/React frontend code with component reuse, design token mapping, TODO-safe business logic, and optional code review.
component-doc-gen
Scan frontend src directories and generate docs/components.md so Claude Code can reuse existing Vue/React components during design-to-code generation.
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.