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 AppsVortex/arness/plugin install arn-sparkWrote 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/appsvortex/arness/arn-spark-style-explore)<a href="https://agentmods.dev/skills/appsvortex/arness/arn-spark-style-explore"><img src="https://agentmods.dev/badge/skills/appsvortex/arness/arn-spark-style-explore/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/appsvortex/arness/arn-spark-style-explore"><img src="https://agentmods.dev/badge/skills/appsvortex/arness/arn-spark-style-explore.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.00096 | $0.04570 |
| Opus 5.5 | $0.00038 | $0.01828 |
| Sonnet 5.5 | $0.00019 | $0.00914 |
| Haiku 4.5 | $0.00010 | $0.00457 |
Grade A, and why
arn-spark-style-explore 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 today.
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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arness Style Explore
Explore visual style direction for the project through iterative conversation, aided by the arn-spark-ux-specialist agent (a greenfield agent in this plugin) for design guidance, optionally the arn-spark-style-capture agent for capturing reference website screenshots, and optionally the arn-spark-prototype-builder agent for sample screens. This is a conversational skill that runs in normal conversation (NOT plan mode). The primary artifact is a style brief document with implementable toolkit configuration.
This skill covers the visual identity of the product: colors, typography, spacing, component customization, and animation approach. It translates these into concrete configuration for the project's CSS framework and component library. It does not create full application screens -- that is /arn-spark-static-prototype and /arn-spark-clickable-prototype's job.
Prerequisites
A product concept document should exist for context on target users and product personality. Check in order:
- Read the project's
CLAUDE.mdfor a## Arnesssection. If found, check the configured Vision directory forproduct-concept.md - If no
## Arnesssection found, check.arness/vision/product-concept.mdat the project root
If a product concept is found: Read it to inform style recommendations.
If no product concept is found: Proceed with the user's description of the product. Style exploration does not hard-require a product concept.
Visual direction (recommended):
- Check the configured Vision directory for
visual-direction.md - If no
## Arnesssection found, check.arness/vision/visual-direction.mdat the project root
If a visual direction is found: Read it. The visual direction provides primary visual grounding from /arn-spark-visual-sketch: selected direction characteristics (color mood, typography feel, component style, layout density), approximate color palette with hex values, CSS variables used in the sketch, screenshot paths in the visual grounding designs/ directory, creative anchors — tone commitment, differentiation anchor, and Design Thinking answers that capture the creative intent behind the direction, and animation and motion context — motion philosophy, key patterns, animation approach used, and whether animation is integral to the direction's identity. Use this as the starting point for style exploration rather than asking the user to describe a direction from scratch. The creative anchors are the direction's DNA — preserve them through token refinement rather than diluting them into generic defaults.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 282 lines · 96 tokens per session scan A 4fa9bae36401
arn-spark-style-explore is a skill published in the GitHub repository AppsVortex/arness (33 stars, last pushed today), licensed MIT. It adds 96 tokens to every session and 4,570 once invoked, about $0.0004 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-10-25.
Other skills, from other repositories
agent-reels
Find animation and video references on 1human, consult a human-agent shared library, and contribute public creations only with prior owner permission.
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard…
aws-architecture-diagram
Generate AWS architecture diagrams in draw.io format. Activates when the user asks to create, generate, or build an architecture diagram, system diagram, or draw.io diagram for AWS services.
figma-variable-audit
Audit Figma variable collections: tier mapping, naming, alias chains, modes, orphans; can fix in place with Figma Console MCP. Triggers: audit my Figma variables, review variable collections, Figma variable health. For token files in code use token-audit.
token-audit
Audit how design tokens are defined: tiers, naming, alias chains, raw values, orphans, DTCG readiness. Triggers: audit my tokens, token architecture review, token health check. Not for code consuming tokens (token-compliance), theme parity (theme-audit) or Figma variables (figma-variable-audit).
codebase-index
Generate machine-readable index files in .ai/index/ (component inventory, uses/usedBy graph, stats) for AI agents. Triggers: index my codebase, build a relationship graph, what depends on what. Not an assessment; for library health use component-audit.