agentmods.dev

lizard-core

lizard-core is a skill for Codex from lizard-build/lizard-mcp. It costs 194 tokens per session (4,194 once invoked), scanned A, original, MIT.

A guide for managing applications and managed databases on the Lizard cloud platform. It explains how workspaces, projects, and deployable services are organized.

In plain words
What is it for?
Deploying GitHub repositories, creating PostgreSQL, Redis, or S3 services, checking logs and events, managing environment settings, scaling services, and running shell commands.
Why use it?
It helps an agent deploy and operate cloud services while using the correct resource structure and deployment limits. It also documents how to manage logs, secrets, domains, scaling, and related services.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: positional $N argument.

not rated 3repo changed 6d ago A scan 194 tokens original MIT

Good fit Deploying GitHub repositories, creating PostgreSQL, Redis, or S3 services, checking logs and events, managing environment settings, scaling services, and running shell commands.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lizard-build/lizard-mcp/core
View source ↗ lizard-build/lizard-mcp lizard.build
Install

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.

Any agent
npx skills add lizard-build/lizard-mcp --skill core
Clone the repo
git clone --depth 1 https://github.com/lizard-build/lizard-mcp

Made for: Codex.

Wrote 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.

agentmods badge for lizard-core

README.md
[![agentmods](https://agentmods.dev/badge/skills/lizard-build/lizard-mcp/core/github.svg)](https://agentmods.dev/skills/lizard-build/lizard-mcp/core)
Your own site
<a href="https://agentmods.dev/skills/lizard-build/lizard-mcp/core"><img src="https://agentmods.dev/badge/skills/lizard-build/lizard-mcp/core/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.

agentmods 80×15 button for lizard-core

Your own site · 80×15
<a href="https://agentmods.dev/skills/lizard-build/lizard-mcp/core"><img src="https://agentmods.dev/badge/skills/lizard-build/lizard-mcp/core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 194 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,194 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00194 $0.04194
Opus 5.5 $0.00078 $0.01678
Sonnet 5.5 $0.00039 $0.00839
Haiku 4.5 $0.00019 $0.00419

Measured 6d ago against content hash ea34289ffb4c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 6d 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.

skills/core/SKILL.md · 309 lines

How it starts

The opening of the file, as written. The whole thing — 309 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. This MCP server exposes the whole platform through 41 tools — deploy a GitHub repo, provision managed Postgres/Redis/S3, and manage logs, metrics, secrets, domains, scaling, and shell exec — scoped to the caller's own workspaces and projects.

Mental model

workspace -> project -> service (app or addon)
  • Workspace — account/org level. A user belongs to one or more (workspace_list).
  • Project — a group of related services in one workspace (project_list, project_create).
  • Service — a deployable unit. Every app deploys from a GitHub repo (service_create with repoUrl) or starts empty and gets a source wired in later (service_set). There is no local tarball-upload path here — unlike the lizard CLI's lizard up, this MCP server can only deploy from a git repo URL, since it has no access to the user's local filesystem.
  • Managed addons — postgres, redis, s3 (addon_create). See Managed addons for each type's env vars.
  • Cross-resource refs — ${{<name>.<KEY>}} resolves at deploy time against the target's merged env. A ref to a missing target or key resolves to an empty string rather than failing the deploy (only circular refs throw). After wiring one, verify the consumer actually got a value — logs_tail or ssh_exec -- env. Stored form is ID-based, so renaming an addon later doesn't break existing refs.

Most tools take a project (name/slug/ID) and service (name/ID) param, resolved by exact name match, not fuzzy — call workspace_list / project_list / service_list first if unsure which one the user means.

No local repo access

Unlike the lizard CLI or a coding agent working in the user's own checkout, this MCP server never sees the user's files. It cannot read package.json, a Dockerfile, or check for a git remote. That means:

  • Ask the user for the repo URL, branch, and any build/start command instead of inferring them from local files.
  • Rely on the platform's own build auto-detection (lizardpack) for common stacks (Go, Node, Python, Rust, Ruby, PHP, Java, static) rather than guessing a buildCommand / startCommand up front — only set those fields if the user states them, or a build actually fails without them.
  • If a build fails, read deploy_events / logs_tail for the real error before proposing a fix.

Read the full file on GitHub · 309 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 6d ago Changed · +24 lines ea34289ffb4c
  2. 13d ago Changed · +26 lines aa6eb3106c96
  3. 1mo ago First seen · 259 lines · 194 tokens per session scan A 0a2d20c6903a

Subscribe to this mod's changes

lizard-core is a skill published in the GitHub repository lizard-build/lizard-mcp (3 stars, last pushed 5d ago), licensed MIT. It adds 194 tokens to every session and 4,194 once invoked, about $0.0008 per session on Opus 5.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.

CloudDatabasesDevOps and cloudai-agentschatgptclaudedeploymentlizardmcp
Related

Other skills, from other repositories

cis-aws-database-3.2

Ensure to Create The Appropriate Deployment Configuration.

CyberStrikeus/CyberStrike · 17 tokens

postgres

Configure DigitalOcean Managed Postgres with bindable variables or schema isolation. Use when setting up databases, creating users, managing permissions, configuring multi-tenant schemas, or troubleshooting database connectivity on App Platform.

digitalocean-labs/do-app-platform-skills · 42 tokens

use-sealos

Deploy and operate apps on Sealos Cloud: sign in to a Sealos account, deploy any project or self-hosted app (from the template store, an official Docker image, or project source code), provision managed databases (PostgreSQL, MySQL, MongoDB, Redis, Kafka), create S3-compatible object storage, expose public HTTPS…

labring/sealos-skills · 151 tokens

deploio-provision

Provisions and connects managed backing services to Deploio apps — PostgreSQL, MySQL, Redis-compatible KVS, OpenSearch, and S3-compatible object storage. This skill should be triggered when the user needs to add a database, cache, or storage service: "add postgres to Deploio", "provision MySQL", "need a database on…

renuo/deploio-claude-plugin · 0 tokens

lizard-core

Creates cloud sandboxes and deploys apps with the lizard CLI. Sandboxes run untrusted or AI-generated code and give an agent its own computer: shell, files, HTTPS URLs for ports, a desktop and browser for computer use, and Claude Code or Codex in the cloud. Deploys cover apps, agents, workers and managed databases…

lizard-build/lizard-cli · 152 tokens

pinecone

Managed vector DB for production RAG and search.

NousResearch/hermes-agent · 13 tokens