baguette AGENTS.md

baguette AGENTS.md is an instructions file for Codex, OpenCode from tddworks/baguette. It costs 3,538 tokens per session, scanned A, original, Apache-2.0.

Development guidance for Baguette that requires test-driven development, or TDD: write a failing test before writing the production code. It also covers naming abstractions and separating third-party input/output code into an adapter.

In plain words
What is it for?
Use it when adding or changing domain types, abstractions, infrastructure adapters, commands, or Swift source code in the project.
Why use it?
It prevents untested changes and keeps outside-system code isolated, making behavior easier to verify and maintain.

Instructions file for CodexOpenCode

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,740 stars · on GitHub

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/tddworks/baguette/agents-md
Clone the repo
git clone --depth 1 https://github.com/tddworks/baguette

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.

agentmods badge for baguette AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/tddworks/baguette/agents-md.svg)](https://agentmods.dev/instructions/tddworks/baguette/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/tddworks/baguette/agents-md"><img src="https://agentmods.dev/badge/instructions/tddworks/baguette/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 3,538 This file is loaded in full into every session.
When invoked 3,538 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.03538 $0.03538
Opus 5 $0.01769 $0.01769
Sonnet 5 $0.00708 $0.00708
Haiku 4.5 $0.00354 $0.00354

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

Security

Grade A, and why

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

AGENTS.md · 136 lines

How it starts

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

AGENTS.md

This file provides guidance to Codex (Codex.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 · 136 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 First seen · 136 lines · 3,538 tokens per session scan A 6f03c578430e

Subscribe to this mod's changes

baguette AGENTS.md is an instructions file published in the GitHub repository tddworks/baguette (1,740 stars, last pushed 4d ago), licensed Apache-2.0. It adds 3,538 tokens to every session, about $0.0177 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

serve-sim AGENTS.md

Instructions for EvanBacon/serve-sim, covering native build notes, e2e testing with agent-browser and e2e testing via the serve-sim cli.

EvanBacon/serve-sim · 919 tokens

Xcode-Build-Optimization-Agent-Skill AGENTS.md

Instructions for AvdLee/Xcode-Build-Optimization-Agent-Skill, covering agent guidance, layout, skills, rules and handoff between skills.

AvdLee/Xcode-Build-Optimization-Agent-Skill · 740 tokens

Xcode-Build-Optimization-Agent-Skill copilot-instructions.md

Instructions for AvdLee/Xcode-Build-Optimization-Agent-Skill, covering repository mission, agent skill requirements, behavior constraints, build optimization focus areas and common issues to flag.

AvdLee/Xcode-Build-Optimization-Agent-Skill · 525 tokens

AppClaw CLAUDE.md

Claude Code instructions for appclawhq/AppClaw, covering claude.md, what is appclaw?, build & run commands, architecture and entry point & cli modes (src/index.ts).

appclawhq/AppClaw · 5,726 tokens

swift-architecture-skill CLAUDE.md

Instructions for efremidze/swift-architecture-skill, covering swift architecture skill, project structure, how the skill works and key conventions.

efremidze/swift-architecture-skill · 422 tokens

swift-architecture-skill AGENTS.md

Instructions for efremidze/swift-architecture-skill, covering agents guidelines for swift architecture skill, working with this repository, 1. understanding the skill, 2. modifying architecture playbooks and 3. testing and validation.

efremidze/swift-architecture-skill · 987 tokens