Borrowing it
Nothing to install: this file belongs to bobbylough/ai-pit-crew. 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/bobbylough/ai-pit-crew/main/CLAUDE.mdgit clone --depth 1 https://github.com/bobbylough/ai-pit-crewWrote 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/bobbylough/ai-pit-crew/claude-md)<a href="https://agentmods.dev/instructions/bobbylough/ai-pit-crew/claude-md"><img src="https://agentmods.dev/badge/instructions/bobbylough/ai-pit-crew/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.00658 | $0.00658 |
| Opus 5 | $0.00329 | $0.00329 |
| Sonnet 5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
ai-pit-crew 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Configuration
This file configures Claude Code's behavior in this repository.
Role
You are a contributor on this project, not the decision-maker. Read AGENTS.md for the full agent contract before starting any work.
Engineering Principles
Primary Goal
Produce maintainable, reliable, secure, production-ready software that is easy to understand, test, operate, and modify.
Core Principles
- Prefer the simplest solution that fully satisfies the requirements
- Follow KISS and YAGNI - do not add functionality, abstractions, or dependencies not currently needed
- Favor proven, stable technologies over custom implementations or trendy alternatives
- Optimize for maintainability, readability, and operational simplicity over cleverness
- Write code for the next developer who must support it
Implementation Standards
- Use clear, descriptive names for variables, functions, classes, files, and modules
- Keep functions and classes focused on a single responsibility
- Follow existing project patterns and conventions unless there is a compelling reason to improve them
- Minimize coupling and unnecessary complexity
- Remove dead code, unused variables, and obsolete comments
Testing
- Add or update automated tests for all meaningful changes
- Prefer TDD when practical
- Test business behavior and expected outcomes, not implementation details
- Ensure all tests pass before considering work complete
- Write tests at each applicable level:
- Unit tests — individual functions and components in isolation
- Integration tests — interactions between modules, services, or layers
- End-to-end tests — full user flows from entry point to expected outcome
- A feature is not complete without coverage at each level that applies to it
Documentation and Observability
- Write self-explanatory code; add comments only for complex business logic, non-obvious decisions, assumptions, or workarounds
- Ensure critical workflows include sufficient logging so production issues can be diagnosed without a debugger
- Keep documentation synchronized with code 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.
- 8d ago First seen · 83 lines · 658 tokens per session scan A 008bb829f19c
ai-pit-crew CLAUDE.md is an instructions file published in the GitHub repository bobbylough/ai-pit-crew (2 stars, last pushed 3mo ago), licensed MIT. It adds 658 tokens to every session, about $0.0033 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.
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.