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 daeryundf2-prog/LAZYANTIGRAVITY --skill ambiencegit clone --depth 1 https://github.com/daeryundf2-prog/LAZYANTIGRAVITYWrote 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/daeryundf2-prog/lazyantigravity/ambience)<a href="https://agentmods.dev/skills/daeryundf2-prog/lazyantigravity/ambience"><img src="https://agentmods.dev/badge/skills/daeryundf2-prog/lazyantigravity/ambience/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/daeryundf2-prog/lazyantigravity/ambience"><img src="https://agentmods.dev/badge/skills/daeryundf2-prog/lazyantigravity/ambience.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.00132 | $0.04317 |
| Opus 5.5 | $0.00053 | $0.01727 |
| Sonnet 5.5 | $0.00026 | $0.00863 |
| Haiku 4.5 | $0.00013 | $0.00432 |
Grade A, and why
ambience-skill scanned grade A with 1 finding 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 19d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: "Layer A ambience-and-typographic-motion reference anchored to the react-bits catalog (reactbits.dev). Stacks on any style skill whenever work adds a hero atmosphere, an animated or shader background, a typo This is a copy
95% identical to ambience-skill — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ambience and Typographic Motion — react-bits-Anchored
interaction-skill.md owns how controls respond: buttons, tabs, menus, modals, toasts. This file owns the other motion quadrant — the hero's atmosphere, the animated background, the way headline copy arrives, the scroll-driven chapter, the material feel of a card under the pointer. design/README.md names the hero focal object and the atmosphere as the two things that most often ship flat; this is where their mechanisms come from. It stacks on top of any Layer A style skill and any Layer B brand exactly like interaction-skill.md and layout-skill.md, and adds ZERO visual direction: color, type, and material still come from the style skill and DESIGN.md.
Load this whenever the deliverable includes: an animated, shader, particle, or grid background; a hero that must feel atmospheric or dimensional; text that reveals, splits, blurs, shimmers, types, counts, scrambles, or loops; scroll-triggered entrances or pinned chapters; spotlight / tilt / glare / glow card surfaces; or the user says "make the hero stunning", "add a living background", "animate the headline", "make it feel premium and alive".
1. The reference contract — never design ambience from memory
react-bits is the ambience benchmark: 170+ open-source React components across four catalog groups (Text Animations, Animations, Backgrounds, Components), each shipped in four variants (JS or TS, CSS or Tailwind) with a public shadcn-compatible registry. Its quality is uneven — most components ship demo colors, and only a minority carry a reduced-motion path — so it is a source of mechanisms, not a source of finished primitives. Improvising a background or a text reveal produces slop the same way improvised styling does; reaching for a 3D engine because the brief said "stunning" is the expensive version of the same mistake. Consult first, extract, then retrofit.
The contract, in order:
- Find the nearest pattern in the routing map (section 3). The live catalog is
https://reactbits.dev/llms.txt; refresh from it when a pattern seems missing — the catalog grows monthly. - Read its real source through the recipe (section 2). Read the
TS-TWvariant; all four variants share one behavior. - Extract the mechanism, not the pixels: the render loop and what drives it (pointer, scroll, time), the shader uniforms or split strategy, what starts and stops the loop, how it sizes to its container, and what it depends on.
- Run the retrofit checklist (section 4). Assume the reduced-motion path, the off-screen pause, and the accessibility contract are missing until you have read them in the source.
- Adapt to the project. Colors, durations, easings, and intensities come from the project
DESIGN.md; react-bits defaults are demo values. A value that is not inDESIGN.mdgets added there first, then used. - No matching pattern? Compose from the nearest two, or state explicitly that the effect is novel and record its mechanism in
DESIGN.mdbefore building it.
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.
- 19d ago First seen · 147 lines · 132 tokens per session scan A 28255c9b9f4b
ambience-skill is a skill published in the GitHub repository daeryundf2-prog/LAZYANTIGRAVITY (14 stars, last pushed 3d ago), licensed MIT. It adds 132 tokens to every session and 4,317 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 95% identical to ambience-skill, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
create-canvas
Create a project Copilot extension canvas for the current workspace.
magic-ui
Use this skill when users want to add, customize, or troubleshoot Magic UI components in React/Next.js projects. It covers component selection, shadcn registry installation (@magicui/), integration patterns, and practical quality checks for accessibility and maintainability.
loft
Loft the shape before cutting steel — answer a design question that prose cannot settle by building a throwaway artifact: a pure logic module in a clickable shell, or structurally different UI variants behind one route. The captain reacts to the artifact; the answer folds into the decision; the artifact never docks.…
moai-design-tools
Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code.
moai-domain-design-dna
Reverse-engineer a reference design — a screenshot, an image set, or a live URL — into a portable Design DNA JSON across three dimensions (measurable tokens, qualitative style, special-rendering effects), then generate a new self-contained artifact from that JSON. Carries the extraction rules (dominance-based colour…
moai-domain-uiux
UI/UX design systems specialist covering accessibility, icons, theming, design tokens, and user experience patterns. Use when working on design systems, WCAG compliance, ARIA patterns, or dark mode theming.