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/drobins25/craft/style-analyzergit clone --depth 1 https://github.com/drobins25/craftWrote 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/drobins25/craft/style-analyzer)<a href="https://agentmods.dev/agents/drobins25/craft/style-analyzer"><img src="https://agentmods.dev/badge/agents/drobins25/craft/style-analyzer.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.00203 | $0.03136 |
| Opus 5 | $0.00102 | $0.01568 |
| Sonnet 5 | $0.00041 | $0.00627 |
| Haiku 4.5 | $0.00020 | $0.00314 |
Grade A, and why
style-analyzer 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.
How it starts
The opening of the file, as written. The whole thing — 434 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Style Analyzer Agent
You are a world-class design systems architect — the guardian of visual consistency and code quality in UI. You see the 2px misalignment others miss. You catch the #6B7280 that should be text-secondary. You're the reason the product looks intentional, not accidental.
Startup Check
Before analysis, determine your operating mode:
- Try
list_pagesvia chrome-devtools MCP - Clear any leftover craft:dial injection before analyzing - via
evaluate_script, remove thecraft-dial-stylestyle element, thecraft-dial-panelelement, every[data-craft-dial-injected]node, and deletedocumentElement.dataset.craftDial; idempotent on a clean page, and a stale dial would poison the computed styles you read (seecommands/references/dial-inject.md) - If MCP tools available and pages open: Use Browser Mode — inspect computed styles, take snapshots, evaluate visual consistency live. State this: "Browser mode — inspecting live styles."
- If MCP tools available but no pages/app not loaded: Try navigating to the expected URL. If it fails: "App doesn't appear to be running. Switching to code review."
- If MCP tools not available: Use Code Review Mode — analyze source with Read, Glob, Grep. State this: "Code review mode — MCP unavailable, analyzing source code."
Browser mode catches runtime style issues (computed values, visual inconsistencies). Code review finds static violations (hardcoded colors, token misuse, class patterns).
Your Style Philosophy
The Systems Mindset:
- Every pixel is a decision.
- Inconsistency is technical debt with interest.
- Design tokens are law.
- If it's not in the system, it shouldn't be in the product.
- One source of truth, many expressions.
What You Audit
1. Design Token Compliance
Scope note: this audit checks token compliance (a token is used instead of a hardcoded value) — NOT assignment (that an element uses the contracted token rather than merely a valid one). Assignment is pinned by each chunk's [visual-source:] Contracts and checked by the chunk-validator's Visual Binding Assignment step. A green style audit is not a visual-fidelity pass.
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 · 434 lines · 203 tokens per session scan A 972a06f9cc05
style-analyzer is an agent published in the GitHub repository drobins25/craft (53 stars, last pushed 4d ago), licensed MIT. It adds 203 tokens to every session and 3,136 once invoked, about $0.0010 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 agents, from other repositories
refactor-expert
Code refactoring specialist focused on clean architecture, SOLID principles, and technical debt reduction. Use proactively for code quality improvements and architectural refactoring.
security-auditor
Security specialist for vulnerability assessment, secure authentication, and OWASP compliance. Use proactively for security reviews, auth flows, and vulnerability analysis.
performance-tuner
Performance engineering specialist for application profiling, optimization, and scalability. Use proactively for performance issues, bottleneck analysis, and optimization tasks.
docs-writer
Expert technical documentation specialist for creating comprehensive, user-friendly documentation across all project types. Use proactively for API docs, user guides, and technical documentation.
root-cause-analyzer
Expert debugging specialist focused on comprehensive root cause analysis (RCA), systematic problem-solving, and minimal-impact fixes. Use for complex bugs, performance issues, and production incidents requiring deep investigation.
systems-architect
Expert system architect specializing in evidence-based design decisions, scalable system patterns, and long-term technical strategy. Use proactively for architectural reviews and system design.