Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/marcusgoll/Spec-Flownpx agentmods add skills/marcusgoll/spec-flow/theme-consistencyWrote 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/marcusgoll/spec-flow/theme-consistency)<a href="https://agentmods.dev/skills/marcusgoll/spec-flow/theme-consistency"><img src="https://agentmods.dev/badge/skills/marcusgoll/spec-flow/theme-consistency/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/marcusgoll/spec-flow/theme-consistency"><img src="https://agentmods.dev/badge/skills/marcusgoll/spec-flow/theme-consistency.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.00050 | $0.02000 |
| Opus 5 | $0.00025 | $0.01000 |
| Sonnet 5 | $0.00010 | $0.00400 |
| Haiku 4.5 | $0.00005 | $0.00200 |
Grade A, and why
theme-consistency 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
- Loading and enforcing theme.yaml values during mockup generation
- Preventing hardcoded colors, spacing, and typography values
- Validating new screens match established patterns
- Locking theme after first screen approval to ensure session-to-session consistency
This prevents the common problem where screens created in different sessions drift in style, creating an inconsistent prototype that undermines the design intent.
<quick_start> <when_to_invoke> Automatically invoke this skill when:
/prototype create [screen]is called and theme.yaml exists- Generating HTML mockup content for any screen
- User requests a new prototype screen in any session
Do NOT invoke when:
- Creating the very first screen (theme not yet established)
- User explicitly requests to reset/modify theme </when_to_invoke>
<basic_workflow>
- Load Theme - Read
design/prototype/theme.yaml - Check Lock Status - If
locked: true, enforce; iffalse, may update - Load Context - Get app_type, core_goal, layout, tone, density
- Generate Screen - Create HTML using theme CSS variables
- Validate - Check for hardcoded values, fix violations </basic_workflow>
<key_rules> NEVER use:
- Hardcoded hex colors:
#3b82f6,#ffffff - Hardcoded RGB:
rgb(59, 130, 246) - Hardcoded spacing:
padding: 17px,margin: 32px - Arbitrary values:
text-[15px],p-[23px]
ALWAYS use:
- Theme CSS variables:
var(--color-primary),var(--space-4) - Shared component classes:
.btn--primary,.card,.form-input - Density classes:
.density-compact,.density-spacious</key_rules> </quick_start>
<detailed_procedures> <theme_loading>
Loading Theme Configuration
When generating any prototype screen, FIRST load the theme:
# Read design/prototype/theme.yaml
theme:
locked: true|false
palette:
primary: "oklch(55% 0.2 250)"
# ... all colors
typography:
heading_font: "Inter, system-ui, sans-serif"
# ... font settings
spacing:
unit: "8px"
# ... spacing scale
tone:
style: "professional" # affects content voice
density: "comfortable" # affects spacing multipliers
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.
- 8d ago First seen · 289 lines · 50 tokens per session scan A 4dd9fda02e07
theme-consistency is a skill published in the GitHub repository marcusgoll/Spec-Flow (92 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 2,000 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-09-03.
Other skills, from other repositories
HTMLHero.skill
A workflow for building a working, previewable first-page hero section—a prominent opening area of a website—from a prompt, brand direction, and visual requirements. It can work with HTML or React projects and treats the hero as the visual template for later pages.
HTMLPPT.skill
A workflow for turning a designed HTML page or existing web project into a multi-page presentation that runs in a browser. It keeps later slides consistent with the first page's visual style.
skill-premium-web-experience
Use for creating, redesigning, or transforming websites into premium, cinematic, conversion-focused web experiences with visual research, storytelling, scroll-driven interaction, responsive design, motion, performance, accessibility, and visual QA.
skill-frontend-ux-guardrails
Use as a frontend UX quality gate for responsive behavior, overflow, accessibility, interaction usability, touch targets, typography, layout stability, mobile behavior, focus states, reduced motion, and final visual validation.
skill-impeccable
Orquestra melhorias de frontend inspiradas no Impeccable a partir de pedidos conversacionais de design, UX, acessibilidade, responsividade, tipografia, layout, cor, motion, clareza, hardening e polish.
skill-modern-ui-patterns
Use for professional frontend UI implementation with modern component composition, interaction states, forms, tables, cards, navigation, dashboards, SaaS surfaces, and maintainable design-system consistency.