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 skills add S1mpleSonny/neon-vibe-motion --skill neongit clone --depth 1 https://github.com/S1mpleSonny/neon-vibe-motionWrote 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/s1mplesonny/neon-vibe-motion/neon)<a href="https://agentmods.dev/skills/s1mplesonny/neon-vibe-motion/neon"><img src="https://agentmods.dev/badge/skills/s1mplesonny/neon-vibe-motion/neon/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/s1mplesonny/neon-vibe-motion/neon"><img src="https://agentmods.dev/badge/skills/s1mplesonny/neon-vibe-motion/neon.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.00050 | $0.02349 |
| Opus 5.5 | $0.00020 | $0.00940 |
| Sonnet 5.5 | $0.00010 | $0.00470 |
| Haiku 4.5 | $0.00005 | $0.00235 |
Grade A, and why
neon 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 1mo 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Neon — Motion Effect Production
Generate .neon files (JSON motion definitions) and render them to video using a headless browser renderer.
Prerequisites
{skill_dir}is the directory where this SKILL.md file is located.
cd {skill_dir}/scripts && npm install && npm link
After setup, neon is available globally. Requires Node.js 18+ and Chromium (installed by Playwright or system Chrome).
Mandatory Reading Before Implementation
STOP — Before writing ANY code, you MUST read the relevant guide files.
This is NOT optional. Do NOT rely on general knowledge or common conventions.
| If you're implementing... | You MUST first read |
|---|---|
| Canvas 2D effects | CANVAS-GUIDE.md |
| WebGL / 3D effects | WEBGL-GUIDE.md |
| Post-processing (bloom, blur, etc.) | POSTPROCESS-GUIDE.md |
| Image/video/model parameters | PARAMETERS.md |
Why this matters: This framework has specific variable names, conventions, and APIs that differ from common standards. For example:
- Post-process uses
vUv,uTexture,uResolution— NOTv_texCoord,u_texture,u_resolution - Shaders fail silently with wrong names
Workflow:
- Identify which features you need (Canvas? WebGL? Post-process?)
- Read the corresponding guide file(s) FIRST
- Then write code following the guide's exact conventions
Workflow
Generate → Validate → Render
1. Read relevant guide file(s) based on features needed
2. Generate .neon file (JSON matching MotionDefinition interface)
3. neon validate <file.neon>
4. neon render <file.neon> -o output.mp4
Iteration
Modify the .neon file (adjust parameters, code, or settings), then re-render.
.neon File Format
Neon Lab exports .neon files with a wrapper structure:
{
"version": "0.1.0",
"exportedAt": 1770198455346,
"conversation": {
"id": "conversation-uuid",
"title": "效果名称",
"messages": [
{
"id": "msg-1",
"role": "assistant",
"content": "效果描述和实现说明",
"timestamp": 1770198455346
}
],
"motion": { /* MotionDefinition — the actual renderable data */ },
"createdAt": 1770193633865,
"updatedAt": 1770193633865
}
}
What ships with it
24 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.
- CANVAS-GUIDE.md 7.6 KB
- EXAMPLES.md 3.8 KB
- PARAMETERS.md 11 KB
- POSTPROCESS-GUIDE.md 3.8 KB
- scripts/bin/commands/render.js 7.2 KB runs code
- scripts/bin/commands/validate.js 1.4 KB runs code
- scripts/bin/harness-path.js 886 B runs code
- scripts/bin/index.js 2.8 KB runs code
- scripts/bin/mime.js 481 B runs code
- scripts/bin/schema.js 4.5 KB runs code
- scripts/harness/assets/harness-BsqbjFTP.js 923 KB runs code
- scripts/harness/draco/draco_decoder.js 703 KB runs code
- scripts/harness/draco/draco_decoder.wasm 279 KB
- scripts/harness/draco/draco_encoder.js 907 KB runs code
- scripts/harness/draco/draco_wasm_wrapper.js 57 KB runs code
- scripts/harness/draco/gltf/draco_decoder.js 500 KB runs code
- scripts/harness/draco/gltf/draco_decoder.wasm 188 KB
- scripts/harness/draco/gltf/draco_encoder.js 932 KB runs code
- scripts/harness/draco/gltf/draco_wasm_wrapper.js 57 KB runs code
- scripts/harness/draco/README.md 1.5 KB
- scripts/harness/h264mp4/h264-mp4-encoder.web.js 1662 KB runs code
- scripts/harness/harness.html 280 B
- scripts/package.json 193 B
- WEBGL-GUIDE.md 1.5 KB
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.
- 1mo ago First seen · 257 lines · 50 tokens per session scan A e085dd4abac9
neon is a skill published in the GitHub repository S1mpleSonny/neon-vibe-motion (58 stars, last pushed 8mo ago), licensed BSD-3-Clause. It adds 50 tokens to every session and 2,349 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…