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-resolvenpx skills add bitjaru/styleseed --skill ss-resolvegit 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-resolve)<a href="https://agentmods.dev/skills/bitjaru/styleseed/ss-resolve"><img src="https://agentmods.dev/badge/skills/bitjaru/styleseed/ss-resolve.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.00068 | $0.00734 |
| Opus 5 | $0.00034 | $0.00367 |
| Sonnet 5 | $0.00014 | $0.00147 |
| Haiku 4.5 | $0.00007 | $0.00073 |
Grade A, and why
ss-resolve 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
Resolve effective StyleSeed context
Use the bundled scripts/resolve-context.mjs; do not hand-compose the rule stack.
- Read
STYLESEED.mdwhen it exists. Confirm missing required selections with the user. - Keep the working directory at the user's project root. Invoke the script by its installed
path; do not
cdinto the skill directory. - Legacy single-artifact projects should prefer
--from-lock STYLESEED.md. Registry projects use.styleseed/project.jsonplus.styleseed/artifacts/*.jsonand must resolve with--artifactor--all; in registry mode, edit project-owned config instead of passing selection overrides. - Read the emitted bundle before building: legacy writes
.styleseed/effective-rules.md; registry writes.styleseed/bundles/<artifact-id>.md. - Preserve the manifest output: legacy uses
.styleseed/manifest.json; registry uses.styleseed/manifests/<artifact-id>.json. - Use
--checkto detect context drift without rewriting files.
node <installed-ss-resolve>/scripts/resolve-context.mjs \
--from-lock STYLESEED.md \
--agent codex
Registry project:
node <installed-ss-resolve>/scripts/resolve-context.mjs \
--project-root . \
--artifact app-dashboard \
--agent codex
Without a lock:
node <installed-ss-resolve>/scripts/resolve-context.mjs \
--agent claude \
--grammar operations-console \
--adapter product-ui \
--domain saas \
--page dashboard \
--recipe enterprise-workbench \
--palette cobalt-instrument \
--key-color "#175CD3" \
--palette-character balanced \
--palette-mode light \
--palette-harmony auto \
--surface-temperature cool \
--profile swiss
Use --list to print supported IDs. --recipe auto maps the selected grammar to a maintained
default; --palette auto maps that recipe to a contrast-verified semantic palette. Pass explicit
values when the product needs a different morphology or color posture. The default
output directory is .styleseed/ in the
project root. For a project-local reference grammar, pass reference:<slug> and ensure
.styleseed/rulesets/<slug>/RULESET.md exists. Registry projects require the full six-file
reference contract: RULESET.md, tokens.json, evidence.json, checks.md,
reference-board.html, and adapter.json.
When a key color is present in flags or the lock, the resolver uses the shared OKLCH generator and
writes .styleseed/palette.json plus .styleseed/palette.css. The manifest records the generation
inputs. The maintained recipe still supplies product posture and semantic restrictions; its fixed
hex values become fallbacks rather than overriding the generated system.
Do not load llms-full.txt after a bundle resolves successfully. Load a larger source document
only when the bundle names an unresolved ambiguity that requires it.
What ships with it
12 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.
- references/artifact-index.schema.json 639 B
- references/artifact.schema.json 4.4 KB
- references/catalog.json 103 KB
- references/manifest.schema.json 2.2 KB
- references/project.schema.json 3.2 KB
- scripts/compiler.mjs 19 KB runs code
- scripts/distribution-integrity.mjs 6.3 KB runs code
- scripts/migrate-project.mjs 17 KB runs code
- scripts/palette-generator.mjs 14 KB runs code
- scripts/project-registry.mjs 3.4 KB runs code
- scripts/resolve-context.mjs 16 KB runs code
- scripts/runtime-contract.mjs 17 KB runs code
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 · 72 lines · 68 tokens per session scan A c151e944140f
ss-resolve is a skill published in the GitHub repository bitjaru/styleseed (939 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 734 once invoked, about $0.0003 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.