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 skills add CodeInfinity1/Stram --skill theme-factorygit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/theme-factory)<a href="https://agentmods.dev/skills/codeinfinity1/stram/theme-factory"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/theme-factory/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/codeinfinity1/stram/theme-factory"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/theme-factory.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00027 | $0.00422 |
| Opus 5.5 | $0.00011 | $0.00169 |
| Sonnet 5.5 | $0.00005 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
theme-factory 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 1mo 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
Theme Factory
Purpose
Design coherent themes that fit a product and remain usable. The assistant should avoid one-note palettes and decorative excess.
When To Use
Use for color/theme systems, dark/light modes, design tokens, typography, component styling, and visual refreshes.
Inputs And Evidence
- Existing CSS/tokens, brand constraints, screenshots, accessibility needs, and target mood.
- Browser verification artifacts.
Tool Map
read_filesearch_workspacetheme_pack_createtheme_pack_inspectfrontend-designbrowser_live_observebrowser_live_screenshotweb-data-extraction
Workflow
- Inspect current token/style structure.
- Use
theme_pack_createto define palette, typography, spacing, radius, component states, contrast checks, and generated CSS variables. - Avoid dominant single-hue themes unless brand requires it.
- Use
theme_pack_inspectbefore applying the theme in existing styling architecture. - Verify contrast, text fit, and layout.
- Document the theme rules when useful.
Native Implementation Boundaries
- Use project-owned CSS/code.
- Do not import Anthropic theme-factory code.
- Do not add styling libraries without approval.
- Theme-pack artifacts are local specs and CSS sidecars; they are not applied to app code until separate edits are made.
Safety And Approval
- Preserve brand/legal requirements.
- Avoid low contrast or motion-heavy themes.
- Keep accessibility in scope.
Verification
- Browser screenshots prove theme application.
- Check major states and viewports.
- Inspect theme-pack artifacts and CSS sidecars before applying.
- Report contrast or responsive gaps.
Failure Modes
- Pretty palette with unreadable text.
- Inconsistent component states.
- Theme changes leaking into unrelated surfaces.
References
- Shortlist item:
theme-factory.
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.
- 1mo ago First seen · 70 lines · 27 tokens per session scan A 6918db711381
theme-factory is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 422 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
design-critique
Use this skill to audit an interface that already exists and say precisely why it looks generated, templated, or unfinished — a scored rubric across composition, typography, color, states, accessibility and copy, ending in a ranked fix list. Triggers: user says "review the design", "critique this UI", "why does this…
motion-interaction
Add purposeful interaction and motion to HTML designs, including state transitions, feedback, navigation, disclosure, and reduced-motion behavior.
von-restorff-effect
Apply the Von Restorff Effect — the element that differs from its neighbours is the one remembered. Use when a single action must dominate. For overall ordering rather than single-element emphasis, use visual-hierarchy.
handoff-spec
Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use design-qa-checklist; for reusable library components use component-spec (design-systems).
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
dark-mode-design
Adapt an existing palette to dark mode — surface elevation, contrast rebalancing, and desaturation rules. Use when you already have a light palette to translate. For building the base palette first, use color-system.