cami: Instructions file for Claude Code

CLAUDE.md

cami CLAUDE.md is an instructions file for Claude Code from lando-labs/cami. It costs 8,443 tokens per session, scanned A, original, MIT.

Repository instructions for developing CAMI, a Go program that manages coding agents through a command-line tool and MCP server.

In plain words
What is it for?
They are for guiding CAMI work across its Go code, MCP integration, agent deployment, builds, tests, and linting.
Why use it?
They explain the project's architecture, supported platforms, development commands, and testing expectations.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions Claude Code.

This is lando-labs/cami's own configuration. It tells Claude Code how to work on cami 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 cami configures →

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/lando/projects/my-app.

Reuse

Borrowing it

Nothing to install: this file belongs to lando-labs/cami. 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/lando-labs/cami/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/lando-labs/cami

Made for: Claude Code.

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 cami CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/lando-labs/cami/claude-md/github.svg)](https://agentmods.dev/instructions/lando-labs/cami/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/lando-labs/cami/claude-md"><img src="https://agentmods.dev/badge/instructions/lando-labs/cami/claude-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.

agentmods 80×15 button for cami CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/lando-labs/cami/claude-md"><img src="https://agentmods.dev/badge/instructions/lando-labs/cami/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 8,443 This file is loaded in full into every session.
When invoked 8,443 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.08443 $0.08443
Opus 5.5 $0.03377 $0.03377
Sonnet 5.5 $0.01689 $0.01689
Haiku 4.5 $0.00844 $0.00844

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

Security

Grade A, and why

cami CLAUDE.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 2mo 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.

CLAUDE.md · 1,044 lines

How it starts

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

CAMI Development - Claude Agent Management Interface

CAMI Source Code Repository

This is the CAMI development repository. You are working on the Go codebase that powers CAMI's MCP server and CLI.


Claude Context: CAMI Developer Assistant

You are assisting with CAMI development - working on the Go codebase that implements the Model Context Protocol (MCP) server and CLI for Claude Code agent management.

Your Focus Areas:

  1. Go Development - Write clean, idiomatic Go code following the project's patterns and conventions.

  2. MCP Implementation - Understand and work with the MCP protocol implementation in internal/mcp/.

  3. Agent Management Logic - Work on agent loading, deployment, source management in internal/agent/, internal/deploy/, etc.

  4. Cross-Platform Support - Ensure code works on macOS, Linux, and Windows.

  5. Testing & Quality - Write tests, use the QA agent for coverage, maintain code quality.

Development Workflow:

  • Use go run ./cmd/cami for local testing
  • The .mcp.json in this repo uses go run for zero-setup development
  • Run make build to compile binary
  • Run make test for tests
  • Run make lint for code quality checks
  • Use deployed agents (qa, agent-architect) for development tasks

Remember: This is the CAMI source code repo. Users install CAMI via releases and get a clean ~/cami-workspace/ workspace with templates from install/templates/.


Architecture Overview

Single Binary, Dual Modes

# MCP Server Mode (primary) - for Claude Code
$ cami --mcp
# Runs as MCP server on stdio for Claude Code integration

# CLI Mode (secondary) - for scripting and quick checks
$ cami list
$ cami deploy frontend backend ~/projects/my-app
$ cami scan ~/projects/my-app

User Workspace Structure

CAMI creates a user workspace at ~/cami-workspace/ during installation:

~/cami-workspace/                          # User workspace (created by installer)
├── CLAUDE.md                    # User-facing CAMI documentation
├── README.md                    # User quick start guide
├── .mcp.json                    # Local MCP config
├── .gitignore                   # Git ignore rules
├── config.yaml                  # CAMI configuration
├── .claude/
│   └── agents/                  # CAMI's own agents
├── sources/                     # Agent sources
│   ├── my-agents/              # User's custom agents
│   ├── team-agents/            # (if added)
│   └── fullstack-guild/        # Example: guild added via add_source

/usr/local/bin/cami             # Binary (on PATH)

Read the full file on GitHub · 1,044 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.

  1. 2mo ago First seen · 1,044 lines · 8,443 tokens per session scan A fc18a8454116

Subscribe to this mod's changes

cami CLAUDE.md is an instructions file published in the GitHub repository lando-labs/cami (14 stars, last pushed 7mo ago), licensed MIT. It adds 8,443 tokens to every session, about $0.0338 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-09-01.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens