LazyCodex is an agent harness for working on complex codebases, combining project memory, planning, execution, and completion checks inside Codex. It is for developers who want structured, repeatable assistance when handling substantial software projects. The catalogue contains the skills, hook, and MCP integration that provide its workflow inside Codex.
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 code-yeongyu/lazycodex --skill ambiencegit clone --depth 1 https://github.com/code-yeongyu/lazycodexWrote 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/code-yeongyu/lazycodex/ambience)<a href="https://agentmods.dev/skills/code-yeongyu/lazycodex/ambience"><img src="https://agentmods.dev/badge/skills/code-yeongyu/lazycodex/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/code-yeongyu/lazycodex/ambience"><img src="https://agentmods.dev/badge/skills/code-yeongyu/lazycodex/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.04244 |
| Opus 5.5 | $0.00053 | $0.01698 |
| Sonnet 5 | $0.00026 | $0.00849 |
| Haiku 4.5 | $0.00013 | $0.00424 |
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 10d 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 How it starts
The opening of the file, as written. The whole thing — 146 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.
- 10d ago First seen · 146 lines · 132 tokens per session scan A 3e6c894109db
ambience-skill is a skill published in the GitHub repository code-yeongyu/lazycodex (3,593 stars, last pushed today), licensed MIT. It adds 132 tokens to every session and 4,244 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-13.
Other skills, from other repositories
frontend-design
Produce intentional, responsive, accessible UI work and perform visual QA instead of generic component assembly.
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
frontend-philosophy
Visual & UI philosophy (The 5 Pillars of Intentional UI). Understand deeply to avoid "AI slop" and create distinctive, memorable interfaces.
migrate-design-prototype
Reproduce a Claude Design prototype or design handoff (HTML/CSS, .dc.html export, tokens, screenshots) inside a Mendix app: build the palette with mxcli theme create --from, then apply classes in pages with MDL. Use when given a design artefact and asked to make the app look like it.
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
extract-design-system
Extract design primitives from a public website and generate starter token files for your project.