agentmods.dev

cli CLAUDE.md

Instructions for working on a command-line tool and its related design-system context service. They describe required changelog entries and the Git branch workflow for user-facing changes.

In plain words
What is it for?
Making and documenting changes to the CLI or its web app, including creating feature branches, updating the changelog, and preparing work for staging.
Why use it?
They clarify where changes should be recorded and how work should move through feature, staging, and production branches. This helps prevent undocumented changes or direct edits to protected branches.

Instructions file

6 1mo ago A scan 266 tokens original MIT
View the source file uselayout/cli
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.

agentmods
npx agentmods add instructions/uselayout/cli/claude-md
Clone the repo
git clone --depth 1 https://github.com/uselayout/cli
Per session 266 This file is loaded in full into every session.
When invoked 266 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00266 $0.00266
Opus 5 $0.00133 $0.00133
Sonnet 5 $0.00053 $0.00053
Haiku 4.5 $0.00027 $0.00027

Measured 2d ago against content hash 526b29883db9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cli 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 2d 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 · 30 lines

What it actually says

@layoutdesign/context

Open source MCP server + CLI that gives AI coding agents structured design system context.

Changelog

REQUIRED: Before finishing any session that includes user-facing changes, add changelog entries to the web app repo:

  • File: /Users/matt/Cursor Projects/Layout/layout-studio/content/changelog/draft.ts
  • Product: cli
  • Categories: new, improved, fixed
  • Write for users, not developers

Git Branching

Branches:

  • main — production. Never push directly. Only merged from staging after testing.
  • staging — integration branch. Staging site deploys from here.
  • staging/<feature> — feature branches. All work happens here.

Workflow (ALL Claude Code sessions MUST follow this):

  1. Start: git checkout -b staging/<short-name> origin/staging
  2. Work: commit and push to your feature branch
  3. Done: merge feature branch into staging, then delete it
  4. Never push directly to staging or main

Branch naming: staging/<short-description> e.g. staging/extraction-fixes

Need another session's changes? git pull origin staging --rebase

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. 2d ago First seen · 30 lines · 266 tokens per session scan A 526b29883db9

Subscribe to this mod's changes

cli CLAUDE.md is an instructions file published in the GitHub repository uselayout/cli (6 stars, last pushed 1mo ago), licensed MIT. It adds 266 tokens to every session, about $0.0013 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.

Git and workflowProductivity
Related

Other instructions, from other repositories

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

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 · 6,785 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,345 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js 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,296 tokens