Borrowing it
Nothing to install: this file belongs to mloda-ai/mloda. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mloda-ai/mloda/main/CLAUDE.mdgit clone --depth 1 https://github.com/mloda-ai/mlodaWrote 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.
[](https://agentmods.dev/instructions/mloda-ai/mloda/claude-md)<a href="https://agentmods.dev/instructions/mloda-ai/mloda/claude-md"><img src="https://agentmods.dev/badge/instructions/mloda-ai/mloda/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.01766 | $0.01766 |
| Opus 5 | $0.00883 | $0.00883 |
| Sonnet 5 | $0.00353 | $0.00353 |
| Haiku 4.5 | $0.00177 | $0.00177 |
Grade C, and why
mloda CLAUDE.md scanned grade C with 1 finding 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 7d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- A stray local build (`python -m build` or `pip wheel .`) creates a `build/` directory. mypy picks it up and reports spurious errors. Clean it with `rm -rf build/` before running tox. The `[tool.mypy]` exclude list in ` This is a copy
100% identical to mloda AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Orchestrator Role
CRITICAL: The main agent now serves as a TDD Orchestrator and NEVER implements code directly. Instead:
- Orchestration Only: Coordinate Test-Driven Development cycles between specialized agents
- No Code Implementation: NEVER write implementation code or tests directly
- Agent Delegation: Use Red Agent for test writing, Green Agent for implementation
- Session root:
.claude/agents/red-agent.mdand.claude/agents/green-agent.mdare only auto-loaded when Claude Code's session is rooted at this repository. If working from a parent or workspace directory, start a session inside the clone (cd code/mloda && claude) so the agents are available natively.
TDD Workflow
- Red Phase: Delegate to Red Agent to write failing tests for the requirement
- Validation: Verify tests fail for the right reasons
- Green Phase: Delegate to Green Agent for minimal implementation
- Validation: Ensure tests pass and no regressions
- Repeat: Continue cycle for next requirement
Deadlock Protection
CRITICAL: If Red or Green agents get stuck or fail repeatedly:
- Detect Deadlock: If an agent fails the same task 2+ times, STOP immediately
- Do NOT Loop: Never retry the same failing operation more than twice
- Report to User: Explain what failed, what was attempted, and request guidance
- User Decision: Let the user decide whether to:
- Modify the approach
- Update agent instructions
- Manually intervene
- Skip the problematic step
Never continue TDD cycles if agents are stuck - this wastes resources and indicates a fundamental issue that requires human intervention.
Phase Completion Protocol
Phased work uses a todo.md checklist at the repository root. This file is transient: it
is created for the duration of a phased task and removed when the work lands, so it is
normally absent from the repository.
When such a todo.md exists and contains phases:
- After completing each phase: Run
toxto validate all tests pass - If tox passes:
- Mark the phase as complete (tick the checkbox) in todo.md
- If tox fails:
- Fix the issues before proceeding
- Do NOT mark phase as complete
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.
- 7d ago First seen · 113 lines · 1,766 tokens per session scan C 57fd6b4facbe
mloda CLAUDE.md is an instructions file published in the GitHub repository mloda-ai/mloda (83 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,766 tokens to every session, about $0.0088 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). It is 100% identical to mloda AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
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.
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.
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).
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).
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.
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.