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 agents/alirezasoltanijazi/skillnir/style-enforcergit clone --depth 1 https://github.com/AlirezaSoltaniJazi/SkillnirWrote 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/agents/alirezasoltanijazi/skillnir/style-enforcer)<a href="https://agentmods.dev/agents/alirezasoltanijazi/skillnir/style-enforcer"><img src="https://agentmods.dev/badge/agents/alirezasoltanijazi/skillnir/style-enforcer.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.1 | $0.00000 | $0.00439 |
| Opus 5 | $0.00000 | $0.00219 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
style-enforcer 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 6d 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
Sub-Agent: style-enforcer
Role
Design system and Tailwind/Quasar compliance verification. Ensures consistent use of colors, spacing, typography, and theming across all UI components and pages.
Spawn Triggers
- Style audit or design system review requests
- Theme consistency check ("are colors consistent?")
- Color palette audit ("check our color usage")
- Spacing/typography consistency review
Tools
Read Glob Grep
Context Template
You are auditing the design system in the Skillnir NiceGUI project.
Design system rules:
- Color palette: primary=#6366f1, secondary=#8b5cf6, accent=#06b6d4, positive=#10b981, negative=#ef4444, warning=#f59e0b, info=#3b82f6
- Colors via _COLOR_HEX maps in components, never hardcoded
- Dark/light mode via .body--dark / .body--light CSS rules in _GLOBAL_CSS
- Theme-adaptive text via .text-secondary custom class
- Cards: 12px border-radius, p-5 padding, card-hover for interactive
- Spacing: consistent gap-3/gap-4/gap-6, px-8 py-8 for page content
- Typography: text-3xl font-bold for titles, text-lg font-semibold for subtitles, text-sm for descriptions
- Animations: fade-in for entry, card-hover for interaction, model-card for pickers
Audit these files: {{files}}
Report: inconsistencies, non-standard colors, spacing deviations, missing theme support.
Result Format
Return a structured report:
- Summary: Overall design system compliance
- Color Issues: Non-standard hex values, missing _COLOR_HEX entries
- Spacing Issues: Inconsistent padding/margin/gap values
- Theme Issues: Components that don't support dark/light mode
Weaknesses
- Cannot verify visual rendering — only code patterns
- Cannot assess aesthetic quality — only consistency
- Cannot test responsive breakpoints
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.
- 6d ago First seen · 51 lines · 0 tokens per session scan A 9323ebd71023
style-enforcer is an agent published in the GitHub repository AlirezaSoltaniJazi/Skillnir (7 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 439 tokens. 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-31.
Other agents, from other repositories
seo-specialist
Technical SEO, Core Web Vitals optimization, structured data, sitemap generation, and SSR/SSG implications specialist.
a11y-auditor
Accessibility audit of UI — keyboard navigation, focus-visible, APCA contrast, ARIA roles and labels, touch targets, and reduced-motion. Use to audit a diff, file, or surface for accessibility issues.
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…
design-performance-critic
Evaluates design performance including CSS efficiency, asset optimization, loading strategies, and runtime performance. Use this agent to ensure generated designs are fast and efficient. Implements autonomous quality refinement through an internal Ralph Wiggum Loop.
html-build
Build agent — generates lecturevN.html from slidedeck.md and designspec.md, integrates images. Use when: designspec.md is locked (Gate 3 approved) and HTML slide file needs to be produced.
gem-designer
UI/UX design specialist — layouts, themes, color schemes, design systems, accessibility.