Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add a-lottes/aSPARK/plugin install asparkWrote 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/a-lottes/aspark/look-and-feel)<a href="https://agentmods.dev/skills/a-lottes/aspark/look-and-feel"><img src="https://agentmods.dev/badge/skills/a-lottes/aspark/look-and-feel/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/a-lottes/aspark/look-and-feel"><img src="https://agentmods.dev/badge/skills/a-lottes/aspark/look-and-feel.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.00063 | $0.00783 |
| Opus 5 | $0.00032 | $0.00392 |
| Sonnet 5 | $0.00013 | $0.00157 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
look-and-feel 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 10d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/look-and-feel — Specify (Designer)
You are running the design check ceremony. The Designer detects bad design before it gets planned — or critiques a UI that already exists.
Input
Optional argument: a feature name, a URL, or paths to screenshots/components.
Steps
- Resolve the feature. If a feature name was given, use
.spark/<feature-name>/. Otherwise: if.spark/holds exactly one feature, use it; if several, ask the user which one. - Pick the mode.
- Mode A (default): design-check the spec. Requires
.spark/<feature-name>/spec.mdto exist — if it doesn't, stop and point the user to/story-time. - Mode B: the user provided a URL, screenshots or component paths — critique the implemented UI. If a URL was given, capture evidence first (screenshots via the available browser tooling) so the agent judges what is actually rendered.
- Mode A (default): design-check the spec. Requires
- Resolve active lenses. The constitution is the single source of truth.
Read the active lenses from
.spark/constitution.md(its Project Profile section); the design-relevant ones areux,seo(content structure) andi18n(text expansion, RTL) — pass those paths in step 4. If there's no constitution, do not apply lenses off a guess — only give a lightweight nudge: name the likely type in one line (e.g. "app-likeweb-app— auxlens would apply") and point the user to/charterto record it. No lens is switched on without a confirmed constitution entry. - Delegate to the Designer. Invoke the
designeragent with the mode, the feature paths, any evidence, and the paths of the design-relevant active lenses (${CLAUDE_PLUGIN_ROOT}/lenses/<name>.md). In Mode A it fills the Design Review section of the spec; in Mode B it returns a findings report. - Relay evidence requests. If the agent asks for missing evidence (screenshots, flows, viewports), get it from the user or the browser and re-invoke.
- Present the findings by severity, each with location, violated rule
and suggested fix. If the Designer raised scope questions, route them
explicitly back to the PO: offer to run
/story-timeon the spec again. - Close the gate (Mode A). With the design review filled in, walk the
SPEC GATE checklist with the user. Required design changes go into the
spec (stories/ACs adjusted via the PO if needed). On the user's explicit
approval, set the spec status to
approved.
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.
- 10d ago First seen · 66 lines · 63 tokens per session scan A 18807257d4d9
look-and-feel is a skill published in the GitHub repository a-lottes/aSPARK (19 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 783 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.
Other skills, from other repositories
rk-house-style
The ENFORCED house design system — one premium look for every frontend, with gates that stop drift (not just advice). Triggers on building or editing a page, component, view, dashboard, screen, form, table, chart, or any UI surface ("build a page", "create a component", "design a dashboard", "make a form", "add a…
brand-design
Brand-aware design system generator that acts as Head of Brand. Translates abstract brand language into a mathematically-validated, implementation-ready design system, writes creative-brief.md as the source of truth for all UI/UX in a project, and optionally compiles it to framework tokens (Tailwind v4 @theme, v3…
scroll-craft
Build premium scroll-driven landing pages for service, product, food, and drink brands. Plan the visitor journey, page grammar, emotional peak, and bespoke signature move. Create dimensional heroes with independent visual planes, restrained motion, and separate mobile composition. Use supplied photos and footage or…
design-standards
Apply production-grade design standards when building or reviewing pages, components, or UI. Use this skill whenever the user asks to build a page, design a component, lay out a section, review the UI, fix the layout, or check design quality. Triggers on build a page, create a component, design a section, hero, card…
ln-75-architecture-diagram-builder
Creates current or target architecture diagrams as the primary deliverable. Not for UI design, architecture audits, or invented structure.
design-system-reference
Style guides and implementation rules for frontend design. Works with design-discovery agent which handles context gathering and VS-based style recommendations. Contains detailed style guides, anti-patterns, and implementation checklists.