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-cli/corenpx skills add lizard-build/lizard-cli --skill coregit clone --depth 1 https://github.com/lizard-build/lizard-cliWhat 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.00248 | $0.05617 |
| Opus 5 | $0.00124 | $0.02808 |
| Sonnet 5 | $0.00050 | $0.01123 |
| Haiku 4.5 | $0.00025 | $0.00562 |
Grade A, and why
lizard-core 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 yesterday.
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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lizard platform
Lizard is a unified cloud for apps, services, agents, and managed databases. All capabilities are exposed through the lizard CLI (npm package @lizard-build/cli). This skill teaches you to drive it. If lizard isn't on PATH, install it: npm install -g @lizard-build/cli.
If $ARGUMENTS is non-empty, treat it as the user's request and act on it. If empty, ask what they want to do on Lizard.
Read this first
This skill documents platform behavior (build pipeline, env precedence, what knobs the API exposes). It does not describe the user's repo.
Before writing commands for a specific project:
- Read the user's
package.json,Dockerfile,requirements.txt, framework config — confirm what already exists before adding flags. - Don't assume scripts/conventions that aren't visible. On the lizardpack auto-detect path,
Procfile(web:line, Python/Ruby) andpackage.json scripts.start(Node) ARE picked up as the start command; on the synthesized-Dockerfile path (buildCommand/startCommandset) neither is read. Ports are inferred only fromEXPOSE, framework defaults, or an explicitPORTenv. - When in doubt, ask the user or run
lizard <cmd> --help --json.
Execution rules
- Prefer the
lizardCLI. For anything not exposed by it, ask the user — don't hit the API directly. - Always pass
--jsonon non-interactive calls. The CLI also auto-switches when stdout isn't a TTY. For streaming commands (lizard upwithout--detach),--jsonproduces one JSON event per line:{ event: "log", line }, terminating with{ event: "done" }/{ event: "error", message };upadditionally emits a final{ event: "deployed" | "failed" | "deploying", status, url }(urlmay benull).lizard logs --jsonis not a stream: it returns the last 200 lines (override with--tail N, max 1000) and exits — do not wait on it expecting more. Need a specific incident? Use--restart latestor--restart <id>. Only stream logs without--jsonif the user actively wants a live tail. - For unfamiliar commands, run
lizard <cmd> --help --jsonfirst — never guess flag shapes. See Discovery. - Resolve context before any mutation.
lizard statusshows the cwd link;lizard ps --jsonshows services in the linked project. Confirm you're targeting the right thing. - For destructive actions (delete service, drop addon, overwrite a project-wide secret, prod restart), confirm intent with the user before executing. The CLI's own prompts fire only on TTY.
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.
- yesterday First seen · 273 lines · 248 tokens per session scan A c09b05bc73a9
lizard-core is a skill published in the GitHub repository lizard-build/lizard-cli (2 stars, last pushed 4d ago), licensed MIT. It adds 248 tokens to every session and 5,617 once invoked, about $0.0012 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
modal-serverless-gpu
Serverless GPU cloud platform for running ML workloads. Use when you need on-demand GPU access without infrastructure management, deploying ML models as APIs, or running batch jobs with automatic scaling.
i18n-lookup
Look up Zeabur platform UI term translations from the dashboard i18n files. Use when writing or reviewing docs that reference UI elements (button labels, tab names, menu items) to ensure docs match the actual platform translations.
translate
Translate documentation pages to all missing locales. Use when a document exists in one locale but needs to be translated to others. Supports --dry-run, single-locale targeting, and incremental updates.
deploy
Deploy the current project to the cloud using Defang. Guides through CLI setup, authentication, compose file creation, stack selection, config management, and deployment.
flow-nexus-platform
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges.
lizard-core
Core Lizard MCP usage guide. Read this before calling any lizard tool. Covers the full app lifecycle (deploy, redeploy, restart, logs, events, scale, secrets, domains, ssh), the workspace -> project -> service model, managed addons (postgres, redis, s3), the build pipeline (lizardpack auto-detect, repo Dockerfile…