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-updatenpx skills add bitjaru/styleseed --skill ss-updategit 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-update)<a href="https://agentmods.dev/skills/bitjaru/styleseed/ss-update"><img src="https://agentmods.dev/badge/skills/bitjaru/styleseed/ss-update.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.00033 | $0.01977 |
| Opus 5 | $0.00016 | $0.00988 |
| Sonnet 5 | $0.00007 | $0.00395 |
| Haiku 4.5 | $0.00003 | $0.00198 |
Grade A, and why
ss-update 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 today.
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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
StyleSeed update
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.
Update the engine payload, not the user's product UI. A release version describes a published
line; engineRevision identifies the exact maintained rules, skills, entry docs, and palette
engine. Two installs with the same release version are not proven equal until their revisions
match.
The checker verifies the payload for the active install channel. A repository/plugin checkout
uses the full core inventory; a project-local Agent Skills install uses the executable skills
inventory. The published endpoint must expose both the engine revision and, for a skills-only
install, skillsRevision. The project manifest continues to record the engine revision that
compiled its method bundle.
The bundled catalog also records distributionSource.channel. edge follows the mutable public
repository state; stable follows the latest published release manifest. Do not compare a stable
archive directly to edge main unless the user explicitly requests a channel switch.
When not to use
- First installation →
/ss-setupor$ss-setup. - One new screen or component →
/ss-build,/ss-page, or/ss-component. - A redesign of old UI → update first, then offer the optional retrofit step below.
- A heavily forked StyleSeed payload → stop after the dry-run report and request a manual diff.
Ownership boundary
StyleSeed owns installed ss-* skill payloads and compiled .styleseed/effective-rules.md.
The project owns STYLESEED.md, application code, components, tokens, assets, and any existing
AGENTS.md, CLAUDE.md, or Cursor instructions. Never overwrite project-owned files merely to
update StyleSeed.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · +8 lines daeaa0c0a210
- 4d ago First seen · 171 lines · 33 tokens per session scan A bf7e6236caf1
ss-update is a skill published in the GitHub repository bitjaru/styleseed (939 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 1,977 once invoked, about $0.0002 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.