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 lizard-build/lizard-studio --skill lizardgit clone --depth 1 https://github.com/lizard-build/lizard-studioWrote 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/lizard-build/lizard-studio/lizard)<a href="https://agentmods.dev/skills/lizard-build/lizard-studio/lizard"><img src="https://agentmods.dev/badge/skills/lizard-build/lizard-studio/lizard/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/lizard-build/lizard-studio/lizard"><img src="https://agentmods.dev/badge/skills/lizard-build/lizard-studio/lizard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high YARA Match · line 72 YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).Fix: Remove the malware payload or compromised file entirely. Investigate how it entered the skill and audit all other artifacts for additional indicators of compromise.
- medium MCP Rug Pull · line 19 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 19 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium Rogue Agent · line 70 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00151 | $0.01758 |
| Opus 5.5 | $0.00060 | $0.00703 |
| Sonnet 5.5 | $0.00030 | $0.00352 |
| Haiku 4.5 | $0.00015 | $0.00176 |
Grade C, and why
lizard scanned grade C with 2 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 8d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://lizard.build/install.sh | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://lizard.build/install.sh | bash How it starts
The opening of the file, as written. The whole thing — 151 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 upgrade --check --json
lizard skills get core --json
The guide ships inside the CLI, so an old CLI teaches old commands (sandbox
templates and old machines often carry one). If the check says
updateAvailable: true, run lizard upgrade --json, then load the guide again.
If that answers upgraded: false with a hint, run the hint (for example
npm install -g @lizard-build/cli@latest). A check that fails (offline,
rate-limited) is no reason to stop: use the guide you have.
lizard skills get core --json returns { name, frontmatter, content, references, ... }. Read content in full - it is the up-to-date Lizard guide to the whole
platform: sandboxes, deploys, addons, sign-in, exit codes, billing. Follow it for
the rest of the task.
references lists three deeper guides: sandboxes, deploys and sdk (building
on Lizard from code). Load one only when the task needs that depth:
lizard skills get core --ref sdk --json
If the CLI rejects --ref (versions before 4.0.45), skip it: on those versions
content already holds everything.
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 beyond the upgrade above. Only drop
to Step 3 if a command actually reports no auth.
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.
- 8d ago Changed · +19 lines b4051c3aef66
- 9d ago Changed · +16 lines · -49 tokens per session scan A → C 44b645b82676
- 1mo 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 (7 stars, last pushed 2d ago), licensed MIT. It adds 151 tokens to every session and 1,758 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
hero-horizon-scan
Grid lines fade in, a glowing horizon locks, and a vertical scan sweeps the frame. Ideal for sci-fi or infrastructure product heroes.
chrome-extension
Use when building or shipping a Manifest V3 browser extension and hitting its quirks — service worker dying and losing state, permission warnings, a Chrome Web Store rejection, content-script/worker/popup messaging, or an MV2-to-V3 migration. NOT a generic web app (that is nextjs), NOT a desktop shell (that is…
incident-response-skill
A skill that uses object-style tool references with purpose descriptions and required flags, plus strict validation.
parallel-subagents
When a task decomposes into independent slices — separate files, OR separate sections of ONE file — fan it out: write job files to the subagent queue and the host runs real parallel Codex workers for you. For a single file, extract per-section slice files into the queue's work/ zone, let workers polish them in…
annotated-rewrite
When editing .tex files, use this skill as often as possible. When rewriting .tex content spanning more than a few words, comment out the original and write the replacement below it so the user can review the before/after diff directly in the source.
overleaf-writing-style-builder
Extract evidence-backed expression habits from selected writing samples, producing a topic-independent style profile and a section-indexed example library.