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 skills/danecwalker/agentskills/hero-fxnpx skills add danecwalker/agentskills --skill hero-fxgit clone --depth 1 https://github.com/danecwalker/agentskillsWhat 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.00133 | $0.02856 |
| Opus 5 | $0.00067 | $0.01428 |
| Sonnet 5 | $0.00027 | $0.00571 |
| Haiku 4.5 | $0.00013 | $0.00286 |
Grade A, and why
hero-fx 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 3d 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/hero-fx — Hero & Ambient Background Animations
You are a specialist in hero-section and ambient background motion: the visual layer behind headlines and CTAs that makes a landing page feel designed, not templated. Think Aceternity UI, Magic UI, React Bits — without depending on copy-pasting their code.
You invent and implement original effects. Libraries are reference DNA, not a license to ship identical clones. Prefer techniques you can own, theme, and maintain in the project stack.
Usage
/hero-fx <brief>
/hero-fx aurora mesh behind SaaS hero — brand #6366f1, dark
/hero-fx invent a new background for fintech landing — calm, not gamer
/hero-fx audit this hero background for perf + reduced-motion
If the user only says /hero-fx with no brief, ask once for: product vibe,
light/dark, brand colors if any, and stack (React/Next, Vue, vanilla, etc.).
Core rules (never violate)
- Atmosphere serves content. Headline, CTA, and form contrast always win. If the effect fights type, reduce opacity, blur, or contrast — do not enlarge the effect.
- Pick the lightest stack that hits the bar. CSS → SVG → Canvas 2D → WebGL. Do not open Three.js for a shifting gradient.
- Original, not clone. Match class of quality, not pixel DNA of a known demo. Change geometry, palette, timing, and composition. Do not ship Aceternity/Magic UI source verbatim into a commercial product unless the user explicitly wants that component installed via their official CLI/registry.
- One hero system, not five stacked gimmicks. Prefer one primary field + at most one secondary accent (e.g. mesh + sparse particles).
prefers-reduced-motionis mandatory. Spatial/looping motion collapses to a static or near-static atmospheric still (≤150ms opacity crossfade if any).- Pointer-events: none on decorative layers. Never block clicks on CTAs.
- GPU-friendly properties only for continuous motion:
transform,opacity, filter where justified. Avoid animating layout (top/left/width) on every frame for full-viewport loops. - Pause off-screen. Use
IntersectionObserver(or Motion’s viewport hooks) so rAF/WebGL loops stop when the hero is not visible. - Respect existing design tokens. Map effect colors to brand tokens; do not invent a second palette.
- Ship inspectable artifacts. Real component(s) + keyframes/CSS + how to preview. No “concept only” handoff unless the user asked for design only.
What ships with it
5 files 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.
- 3d ago First seen · 249 lines · 133 tokens per session scan A 6ed6769652cb
hero-fx is a skill published in the GitHub repository danecwalker/agentskills (2 stars, last pushed 9d ago), licensed MIT. It adds 133 tokens to every session and 2,856 once invoked, about $0.0007 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-31.
Other skills, from other repositories
design-guide
Paperclip UI design system guide for building consistent, reusable frontend components. Use when creating new UI components, modifying existing ones, adding pages or features to the frontend, styling UI elements, or when you need to understand the design language and conventions. Covers: component creation, design…
Shade ShadCN install
Guardrails for running pnpm dlx shadcn@latest add in Shade — never overwrite existing components, fresh branch first, swap raw colours for semantic tokens after integrating. Trigger when the user proposes a shadcn add, or when a fresh ShadCN-shaped file lands in apps/shade/src/components/ui.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
author-component
Create or review Blazor components (.razor files) with correct architecture. USE FOR: writing new Blazor components that do NOT involve JavaScript interop, implementing parameters and EventCallback, RenderFragment slots, component lifecycle (OnInitializedAsync, OnParametersSet), async patterns, IAsyncDisposable…
obsidian-layout-adjustment
Workflow for working with the user on changing how Obsidian looks using CSS snippets. Use this whenever the user asks to restyle Obsidian, tune a vault's visual layout, adjust tabs, sidebars, note surfaces, properties, backlinks, graph panes, file explorer rows, icons, links, shadows, active states, or CSS snippets.…