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/lizard-build/lizard-studio/lizardnpx skills add lizard-build/lizard-studio --skill lizardgit clone --depth 1 https://github.com/lizard-build/lizard-studioWhat 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.00200 | $0.01242 |
| Opus 5 | $0.00100 | $0.00621 |
| Sonnet 5 | $0.00040 | $0.00248 |
| Haiku 4.5 | $0.00020 | $0.00124 |
Grade A, and why
lizard 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 2d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lizard - bootstrap
This is a thin entry point. The authoritative guide lives inside the lizard CLI
and is versioned with it, so it always matches the installed CLI version.
Be optimistic: assume the CLI is already available. Try to load the core guide first; only fall back to install / permission help when a command actually fails.
Do NOT improvise lizard commands from this file - the full instructions, flags,
and exit codes come from the loaded core guide.
Never run the CLI via npx (npx @lizard-build/cli, npx lizard, etc.).
Always use the globally installed lizard binary. npx pulls a throwaway copy
into a cache, whose version may not match the loaded guide and which bypasses the
install flow below. If lizard is not on PATH, install it (step 2a) - do not
reach for npx, even just to check whether it works.
Step 1 - Load the core guide (try first)
Run immediately:
lizard skills get core --json
This returns { name, frontmatter, content, ... }. Read content in full - it is
the complete, up-to-date Lizard usage guide (build pipeline, env precedence,
addons, discovery, exit codes, everything). Follow it for the rest of the task.
If it loads, skip the recovery in Step 2 and go straight to Step 4 to act -
assume the user is already logged in. Do not run command -v lizard, do not log
in preemptively, and do not install anything. Only drop to Step 3 if a command
actually reports no auth.
Step 2 - Recover only on failure
Handle failures from step 1 in order. Stop as soon as one path works and return to the guide.
2a. lizard: command not found (CLI not on PATH)
Install it globally, then retry step 1:
npm install -g @lizard-build/cli
2b. Permission denied (EACCES) on global install
Do NOT retry with sudo. Ask the user to run the install themselves in their
own terminal (in agents that support in-session shell passthrough, e.g. Claude
Code or Cursor, they can type ! npm install -g @lizard-build/cli):
What ships with it
2 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.
- 2d ago First seen · 116 lines · 200 tokens per session scan A 9d38233ec6fd
lizard is a skill published in the GitHub repository lizard-build/lizard-studio (5 stars, last pushed 5d ago), licensed MIT. It adds 200 tokens to every session and 1,242 once invoked, about $0.0010 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
livecodes/self-hosting
Deploy LiveCodes to static servers, GitHub Pages, or Docker. Configure SDK appUrl, BASEURL for subdirectories, and handle share/broadcast services. Load this skill when self-hosting LiveCodes or using a custom app URL.
update-chrome-binaries-test-region
Publish Remotion Lambda Chrome binaries to the eu-central-1 test region and update hosted layer and Chrome version references. Use when updating Chrome binaries before full regional rollout.
vercel
Set up a Codex monitor for Vercel deployments and preview URLs. Use when the user invokes /vercel or $vercel, asks Codex to watch or monitor a Vercel deployment, waits for a Vercel preview or PR preview to become ready, or wants to be notified with both the deployment URL and preview URL once Vercel is READY.
offload-r2
Upload Remotion repository media assets to the Cloudflare R2 bucket behind remotion.media, switch source code to hosted URLs, verify the public objects, and remove repository-local copies.
upload-r2
Upload large Remotion repository assets to the Cloudflare R2 bucket behind remotion.media and replace local public/ assets with hosted URLs. Use when a file is too large for Git or when a PR should avoid committing media binaries by hosting them on remotion.media.
configure-factory-rules
Configure typed Mastra Factory rules and exact-leaf overrides in deployment code.