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 interactiongit 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/interaction)<a href="https://agentmods.dev/skills/code-yeongyu/lazycodex/interaction"><img src="https://agentmods.dev/badge/skills/code-yeongyu/lazycodex/interaction/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/interaction"><img src="https://agentmods.dev/badge/skills/code-yeongyu/lazycodex/interaction.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.00104 | $0.03097 |
| Opus 5.5 | $0.00042 | $0.01239 |
| Sonnet 5 | $0.00021 | $0.00619 |
| Haiku 4.5 | $0.00010 | $0.00310 |
Grade A, and why
interaction-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.
[beui.dev](https://beui.dev) is the interaction benchmark: free, open-source animated React components (Motion + Tailwind CSS) where every component ships reduced-motion support and the full TypeScript source is one `cur 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.
Interaction Mechanics — beui.dev-Anchored
Style skills decide how a surface looks. This file decides how it moves and responds — spring physics, layout morphs, enter/exit orchestration, gesture feel, and reduced-motion discipline. It stacks on top of any Layer A style skill and any Layer B brand, exactly like 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 interaction feel: micro-interactions, animated components, transitions, hover/press/focus/state feedback, gestures, loading/success/error morphs, animated tabs/menus/modals/drawers/toasts — or the user says "make it feel alive", "polish the interactions", "add micro-interactions".
1. The reference contract — never design an interaction from memory
beui.dev is the interaction benchmark: free, open-source animated React components (Motion + Tailwind CSS) where every component ships reduced-motion support and the full TypeScript source is one curl away. Improvised interaction design produces slop motion the same way freestyled styling produces generic SaaS slop, and the fix is the same: consult the reference before designing.
The contract, in order:
- Find the nearest pattern in the catalog (section 3). The live catalog is
https://beui.dev/llms.txt; refresh from it when a pattern seems missing from the tables below. - Read its real source through the recipe (section 2). Never guess spring values, exit orchestration, or gesture thresholds from a preview description.
- Extract the mechanism, not the pixels: the spring config, the layout strategy (
layoutIdshared layout vs height morph vs clip-path), what animates in what order on enter/exit, where blur crossfades sit, and what the reduced-motion path swaps to. - Adapt to the project. Concrete durations, easings, and spring params come from the project
DESIGN.mdMotion & Interaction section. Where beui.dev andDESIGN.mddisagree,DESIGN.mdwins. 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 interaction 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 · 147 lines · 104 tokens per session scan A 26a5f9cffa08
interaction-skill is a skill published in the GitHub repository code-yeongyu/lazycodex (3,593 stars, last pushed today), licensed MIT. It adds 104 tokens to every session and 3,097 once invoked, about $0.0004 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.