baguette: Instructions file for Claude Code

CLAUDE.md

baguette CLAUDE.md is an instructions file for Claude Code from tddworks/baguette. It costs 4,386 tokens per session, scanned A, original, Apache-2.0.

A repository instruction document that requires test-driven development, or TDD: write a test that fails before writing the production code that should make it pass. It also defines rules for naming abstractions and separating third-party input/output adapters.

In plain words
What is it for?
Use it when changing the Baguette codebase, especially domain types, interfaces, infrastructure adapters, or application commands.
Why use it?
It makes expected behavior explicit before implementation and helps keep external-system code isolated and testable.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

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

About the project

Baguette is a command-line tool and web interface for controlling iOS simulators without opening Xcode or Simulator.app. Developers and agents use it to boot devices, stream screens, send touch and hardware input, inspect accessibility data and logs, and capture screenshots or recordings. The catalogue includes skills, instructions, and a plugin for operating Baguette.

tddworks/baguette · 1,745 stars · on GitHub · tddworks.github.io

Reuse

Borrowing it

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

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

README.md
[![agentmods](https://agentmods.dev/badge/instructions/tddworks/baguette/claude-md.svg)](https://agentmods.dev/instructions/tddworks/baguette/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/tddworks/baguette/claude-md"><img src="https://agentmods.dev/badge/instructions/tddworks/baguette/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 4,386 This file is loaded in full into every session.
When invoked 4,386 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.04386 $0.04386
Opus 5 $0.02193 $0.02193
Sonnet 5 $0.00877 $0.00877
Haiku 4.5 $0.00439 $0.00439

Measured 5d ago against content hash 30f02cbf4be0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

baguette 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 5d 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 · 132 lines

How it starts

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

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

TDD is non-negotiable (read this first)

You MUST write a failing test before writing any production code. This rule overrides every other instinct, including "the change is small", "it's just a one-liner", "I'll add the test after". If you catch yourself opening a file under Sources/Baguette/ before a test under Tests/BaguetteTests/ exists and fails, stop and reverse course.

Pre-implementation gate — before editing anything in Sources/ (Domain value type, Domain abstraction, Infrastructure adapter, App-layer command), you must have done all of the following in order:

  1. Stated the user-facing behaviour in one sentence using domain language, not implementation language. Good: "a tap is dispatched as down → hold → up against the input surface", "describe-ui returns nil when no app is frontmost", "logs reject notice because the iOS-runtime log binary doesn't accept it". Bad: "IndigoHIDInput calls sendMouse twice" — that's an interaction, not a behaviour.
  2. Written a @Test in Tests/BaguetteTests/<Context>/<Suite>.swift that asserts the expected outcome. Prefer state assertions (#expect(filter.argv == [...]), #expect(node.frame == ...)) over interaction assertions. For @Mockable abstractions, use the auto-generated MockXxx (given(input).tap(...).willReturn(true)); plain test doubles backed by Mockable are the canonical mocking style — never mock the value type itself.
  3. Run the test and observed it failswift test --filter "<SuiteName>" for the fastest loop. A compile error counts as red only when the failing symbol is the one the test names (KeyboardKey.from(wireCode:) doesn't exist yet); a generic build error somewhere else doesn't.
  4. Reported the red result back to the user (one line is fine: "test parses lowercase letter wire codes onto HID page 7 fails: KeyboardKey.from is not a member").

Only after step 4 may you write code under Sources/. Pure docs / CHANGELOG edits and Resources/Web/ JS tweaks are exempt; the moment a Domain type, Infrastructure adapter, or App command changes, the gate applies.

Read the full file on GitHub · 132 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. 5d ago Changed · +1 tokens per session 30f02cbf4be0
  2. 7d ago First seen · 132 lines · 4,385 tokens per session scan A c76cd1f3cb9a

Subscribe to this mod's changes

baguette CLAUDE.md is an instructions file published in the GitHub repository tddworks/baguette (1,745 stars, last pushed 6d ago), licensed Apache-2.0. It adds 4,386 tokens to every session, about $0.0219 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-30.

Related

Other instructions, from other repositories

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

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,296 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,469 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

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