cezar: Skill for Claude Code

.ai/skills/om-prepare-test-env/SKILL.md

om-prepare-test-env is a skill for Claude Code, Codex from open-mercato/cezar. It costs 0 tokens per session (214 once invoked), scanned A, original, MIT.

A test-environment setup guide for Cezar, a system that coordinates coding agents such as Claude Code, Codex, and OpenCode. It describes how to start the application reliably and prepare dependencies in fresh workspaces.

In plain words
What is it for?
Use it when preparing or validating Cezar’s local test environment, rebuilding fresh worktrees, checking the web build, and running quality assurance with locked agent models.
Why use it?
It prevents test servers from stopping unexpectedly and avoids build failures caused by missing workspace links, dependencies, or incomplete cache checks.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is open-mercato/cezar's own configuration. It tells Claude Code and Codex how to work on cezar itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything cezar configures →

Reuse

Borrowing it

Nothing to install: this file belongs to open-mercato/cezar. 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/open-mercato/cezar/main/.ai/skills/om-prepare-test-env/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/open-mercato/cezar

Made for: Claude Code, 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 om-prepare-test-env

README.md
[![agentmods](https://agentmods.dev/badge/skills/open-mercato/cezar/om-prepare-test-env/github.svg)](https://agentmods.dev/skills/open-mercato/cezar/om-prepare-test-env)
Your own site
<a href="https://agentmods.dev/skills/open-mercato/cezar/om-prepare-test-env"><img src="https://agentmods.dev/badge/skills/open-mercato/cezar/om-prepare-test-env/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 om-prepare-test-env

Your own site · 80×15
<a href="https://agentmods.dev/skills/open-mercato/cezar/om-prepare-test-env"><img src="https://agentmods.dev/badge/skills/open-mercato/cezar/om-prepare-test-env.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 214 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00000 $0.00214
Opus 5 $0.00000 $0.00107
Sonnet 5 $0.00000 $0.00043
Haiku 4.5 $0.00000 $0.00021

Measured 9d ago against content hash 91787ec97710, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

om-prepare-test-env 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 9d 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.

.ai/skills/om-prepare-test-env/SKILL.md · 5 lines

What it actually says

Repository test-environment notes

  • Launch the built cezar server through .ai/scripts/test-env-up.sh; its app process must use nohup with stdin detached so it survives non-interactive bootstrap shells. This prevents a descriptor from reporting a server that is terminated as soon as the bootstrap command exits.
  • Fresh worktrees have no workspace links or runtime dependencies. The generated entrypoint must run the compound npm ci && npm run build chain through sh -c, include packages/contract/src in its build fingerprint, and require node_modules/zod/package.json as a cache artifact. This prevents @open-mercato/cezar-contract from resolving as missing/unknown during tsc and prevents a cached build from starting without runtime dependencies. Do not require packages/api-client/dist: the web build aliases that workspace to source and the root build does not emit that directory. Run CEZ_AGENT_MODELS_LOCKED=1 sh .ai/scripts/test-env-up.sh --force for locked-model QA.
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. 9d ago First seen · 5 lines · 0 tokens per session scan A 91787ec97710

Subscribe to this mod's changes

om-prepare-test-env is a skill published in the GitHub repository open-mercato/cezar (183 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 214 tokens. 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-30.

Related

Other skills, from other repositories

using-ao

Catalog of the AO (Agent Orchestrator) ao CLI: spawning workers, managing sessions and projects, sending messages, controlling the shared browser, previewing pages, and daemon control. Use when using the ao CLI, spawning workers, or managing AO sessions in an AO workspace.

Untrivial-ai/agent-orchestrator · 62 tokens

standup-update

Generate a concise standup update from the user's recent work GitHub activity, including the previous work period and today. Use when the user asks what they worked on, requests a standup update, or invokes /standup.

gszr/lunar · 49 tokens

ship

Fully automated ship workflow. Merges the base branch, runs tests, audits coverage, reviews the diff, generates a CHANGELOG entry, bumps the version, commits, pushes, and creates the PR. Use when asked to "ship", "create a PR", or "open a pull request".

HECer/yoke · 61 tokens

seam-onboard

Install Seamless awareness for the current agent client. Use only when the user explicitly asks to onboard Seamless or invokes this skill. Configure the client's hooks and MCP server if needed, ask whether guidance belongs globally or in this project, append a marker-wrapped block to AGENTS.md for Codex or CLAUDE.md…

0spoon/seamless · 77 tokens

plan-eng-review

Engineering plan review. Reviews a plan document for architecture, code quality, test coverage, and performance before implementation begins. Produces a coverage diagram, failure modes map, and parallelization strategy. Use when asked to "review this plan", "eng review", or "architecture review".

HECer/yoke · 61 tokens

retro

Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics for the time window. Team-aware: identifies the user, then analyzes every contributor with per-person praise and growth opportunities. Use when asked for a "retro", "engineering retrospective", or "weekly summary".

HECer/yoke · 63 tokens