ss-resolve

ss-resolve is a skill for Claude Code, Codex from bitjaru/styleseed. It costs 68 tokens per session (734 once invoked), scanned A, original, MIT.

A tool that selects and compiles the StyleSeed design rules needed for one project task. It combines choices such as layout grammar, surface style, domain, page type, brand, palette, and an optional visual profile.

In plain words
What is it for?
Use it before building or after changing StyleSeed settings to generate the effective rules and preserve a record of the selected design context.
Why use it?
It keeps the working rule set small and consistent instead of making the agent load and interpret the entire design handbook. It also detects when the project’s design context has changed.

Skill for Claude CodeCodex

Part of the styleseed plugin — 24 skills shipped together

Install

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.

agentmods
npx agentmods add skills/bitjaru/styleseed/ss-resolve
Any agent
npx skills add bitjaru/styleseed --skill ss-resolve
Clone the repo
git clone --depth 1 https://github.com/bitjaru/styleseed

Made for: Claude Code, Codex.

Or install styleseed, the plugin that ships this one along with the rest of its 24 skills.

Wrote 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.

agentmods badge for ss-resolve

README.md
[![agentmods](https://agentmods.dev/badge/skills/bitjaru/styleseed/ss-resolve.svg)](https://agentmods.dev/skills/bitjaru/styleseed/ss-resolve)
Your own site
<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>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 734 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 4d ago against content hash c151e944140f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

The scan reads SKILL.md. This mod also ships 7 executable files (scripts/compiler.mjs, scripts/distribution-integrity.mjs, scripts/migrate-project.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

engine/.claude/skills/ss-resolve/SKILL.md · 72 lines

What it actually says

Resolve effective StyleSeed context

Use the bundled scripts/resolve-context.mjs; do not hand-compose the rule stack.

  1. Read STYLESEED.md when it exists. Confirm missing required selections with the user.
  2. Keep the working directory at the user's project root. Invoke the script by its installed path; do not cd into the skill directory.
  3. Legacy single-artifact projects should prefer --from-lock STYLESEED.md. Registry projects use .styleseed/project.json plus .styleseed/artifacts/*.json and must resolve with --artifact or --all; in registry mode, edit project-owned config instead of passing selection overrides.
  4. Read the emitted bundle before building: legacy writes .styleseed/effective-rules.md; registry writes .styleseed/bundles/<artifact-id>.md.
  5. Preserve the manifest output: legacy uses .styleseed/manifest.json; registry uses .styleseed/manifests/<artifact-id>.json.
  6. Use --check to 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.

Changes

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.

  1. 4d ago First seen · 72 lines · 68 tokens per session scan A c151e944140f

Subscribe to this mod's changes

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.