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 commands/f0d010c/stark/stark-assetsgit clone --depth 1 https://github.com/f0d010c/starkWrote 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/commands/f0d010c/stark/stark-assets)<a href="https://agentmods.dev/commands/f0d010c/stark/stark-assets"><img src="https://agentmods.dev/badge/commands/f0d010c/stark/stark-assets.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.00031 | $0.00441 |
| Opus 5 | $0.00015 | $0.00220 |
| Sonnet 5 | $0.00006 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
stark-assets 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.
What it actually says
/stark-assets
Legacy Claude Code command. In Codex, ask:
Use stark assets to plan the visual assets for this app/site before building.
Plan assets for the project described by $ARGUMENTS.
Read:
references/ui-patterns/ui-decision-brief.mdreferences/ui-patterns/asset-selection.mdreferences/ui-patterns/asset-realism-matrix.mdreferences/ui-patterns/asset-production-pipeline.mdreferences/ui-patterns/advanced-visual-systems.mdwhen assets become the signature visual system- the routed platform or web skill
Then produce an asset plan before implementation:
Asset plan
- Needed assets: product UI mock, icons, texture, typeface, references
- Source: local Stark library, lucide, generated CSS/SVG mock, imagegen, external reference
- Advanced visual system: main mechanic, owner, motif, fallback, rejected spectacle, if relevant
- License risk: none / low / needs attribution / avoid
- Usage: hero product preview, warning states, workflow diagram, empty state
- Reference extraction: structure only, not copied visuals
- Bans: stock hero photos, abstract AI gradients, placeholder images, private screenshots without permission
Rules
- Do not freely browse and grab assets.
- Ask whether the project needs icons, real product screenshots, reference UI patterns, typography, brand assets, or generated bitmap visuals.
- Pull only assets that support the product job and visual direction.
- If the agent is GPT/Codex and image generation is available, prefer generated bitmap assets for fictional hero imagery, textures, product concept art, or editorial visuals when CSS/SVG would be too weak.
- Never include private/local screenshots unless the user explicitly allows it.
- Do not copy copyrighted brand assets into public output.
- Use real-world references to extract structure and interaction patterns, not visual identity.
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 · 46 lines · 31 tokens per session scan A 15527f60cee0
stark-assets is a command published in the GitHub repository f0d010c/stark (25 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 31 tokens to every session and 441 once invoked, about $0.0002 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 commands, from other repositories
gen-video
Generate video output in one of three modes: Remotion (programmatic React-based video), Gen-AI (shot prompt pack for Runway/Kling/Sora/Pika/Luma), or Remotion+Gen-AI (programmatic scaffold with AI footage embedded).
brand-generate
Generate an on-brand document from a saved Brand Profile.
video
WATCH a video and return a structured VISUAL breakdown (not just a transcript) with Antigravity (agy / Gemini 3.x, natively multimodal in video). Scene-by-scene segments with timestamps, on-screen text/OCR (slides, charts, UI, captions), key visual events, and a summary. For screencasts, tutorials, presentations…
illustration-system
Design an illustration style guide, icon system, or SVG asset set for a product or brand.
sip-attest-audio
Attest an audio artifact (music track, voice-over, podcast, soundscape). Generates SIP attestation embedded in ID3 tags + sidecar .sip.json. Refuses decorative use. v7.5+ — scaffold present, full implementation pending.
anti-slop-designer
Use when a UI looks machine-made rather than decided. Violet gradients, glassmorphism everywhere, identical cards in a grid, untouched shadcn or Material defaults, emoji bullets, or copy stuffed with seamless and unlock.