What is lizard-cli AGENTS.md?

Repository instructions for developing the lizard-cli command-line tool. They describe its npm-based setup, TypeScript layout, commands, tests, and required JSON output mode.

Use them when modifying lizard-cli, adding commands, building the CLI, or running its integration and unit tests.

They help coding agents follow the project's expected files, package manager, build process, and output conventions. This reduces changes that conflict with the repository's workflow.

How lizard-build/lizard-cli configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to lizard-build/lizard-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/lizard-build/lizard-cli/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/lizard-build/lizard-cli

Made for: Codex, OpenCode.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/lizard-build/lizard-cli/agents-md/github.svg)](https://agentmods.dev/instructions/lizard-build/lizard-cli/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/lizard-build/lizard-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/lizard-build/lizard-cli/agents-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/lizard-build/lizard-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/lizard-build/lizard-cli/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,670 This file is loaded in full into every session.

When invoked 1,670 The same file — it is already loaded in full.

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.

Model	Per session	Once invoked
Fable 5.1	$0.01670	$0.01670
Opus 5.5	$0.00668	$0.00668
Sonnet 5.5	$0.00334	$0.00334
Haiku 4.5	$0.00167	$0.00167

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

Security

Grade A, and why

lizard-cli AGENTS.md 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 23d 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.

AGENTS.md · 118 lines

How it starts

The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Instructions for AI coding agents working in this repo (@lizard-build/cli).

Package manager

This project uses npm. Don't introduce pnpm/yarn lockfiles. Scripts:

npm run build — TypeScript compile to dist/
npm run dev — run from source via tsx
npm test — local unit tests (test/unit/*)
npm run test:integration — live API tests; requires LIZARD_LIVE_TESTS=1. Mutations also require an approved test project in LIZARD_TEST_PROJECT_ID and LIZARD_TEST_ALLOW_MUTATIONS=1.
npm run test:unit — unit tests (test/unit/*)

The published bin is dist/index.js. Always run npm run build before testing against dist/.

Project layout

src/
  index.ts          # Commander root, banner, preAction (auth + JSON mode), --help --json dump
  commands/<name>.ts  # one file per top-level command; exports register<Name>(program)
  lib/
    api.ts          # fetch wrapper, APIError
    auth.ts         # token store, requireAuth()
    config.ts       # ~/.lizard/config.json read/write
    format.ts       # printJSON, isJSONMode, success/error/info/warn, table, statusColor
    picker.ts       # interactive @clack pickers
    resolve.ts      # resolve workspace/project/service from flags or linked dir
    updater.ts      # self-update (precompiled binary only — see note below)
skill-data/<name>/SKILL.md   # agent skills served by `lizard skill get <name>`
skill-data/<name>/references/<ref>.md  # deeper guides served by `lizard skill get <name> --ref <ref>`
dist/               # tsc output, committed; this is what npm ships
test/cli.test.ts    # integration tests (spawn the CLI)
test/unit/*.test.ts # unit tests

Code style

Kebab-case for CLI flags (--service-name, never --serviceName).
No emojis in code, output, or docs. Unicode glyphs (✓, ✗, →) via chalk are fine.
Colors: use chalk and lib/format.ts helpers. Never hardcode ANSI escapes.
info/success/warn/error write to stderr; payload (printJSON, table rows) goes to stdout. Pipes (| jq, > file) must work.
Strict TypeScript. No any in new code unless interacting with commander's loose types.

Read the full file on GitHub · 118 lines

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.

23d ago Changed · +3 lines · +154 tokens per session d67d12289cfd
1mo ago Changed · +1 lines · +72 tokens per session d1ed74991471
2mo ago First seen · 114 lines · 1,444 tokens per session scan A 464089244890

Subscribe to this mod's changes

lizard-cli AGENTS.md is an instructions file published in the GitHub repository lizard-build/lizard-cli (4 stars, last pushed 2d ago), licensed MIT. It adds 1,670 tokens to every session, about $0.0067 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.

Cloud ai-agents cli deployment developer-tools lizard

lizard-cli AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
lizard-cli AGENTS.mdlizard-build/lizard-cli	Instructions file	4	2d ago	MIT	A	1,670	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

lizard-cli: Instructions file for Codex