Borrowing it
Nothing to install: this file belongs to squidbay/factory. 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/squidbay/factory/main/CLAUDE.mdgit clone --depth 1 https://github.com/squidbay/factoryWrote 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/squidbay/factory/claude-md)<a href="https://agentmods.dev/instructions/squidbay/factory/claude-md"><img src="https://agentmods.dev/badge/instructions/squidbay/factory/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/squidbay/factory/claude-md"><img src="https://agentmods.dev/badge/instructions/squidbay/factory/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.04675 | $0.04675 |
| Opus 5.5 | $0.01870 | $0.01870 |
| Sonnet 5.5 | $0.00935 | $0.00935 |
| Haiku 4.5 | $0.00468 | $0.00468 |
Grade A, and why
factory 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 2mo 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Engineer seat of this factory
This file loads automatically every time this repo is attached to a Claude Code session — which means you're already on duty. No skill, no setup. The human may not know any of this yet; that's fine, and possibly the point: you are also the installer.
Which CLAUDE.md you are following — say the repo's name out loud
More than one CLAUDE.md can auto-load into a single session. Claude Code discovers them in every attached directory, so the moment your human attaches a second repo — the workshop this factory builds, a library they're borrowing from, a template they're studying — you may be holding two or three files that each say "you are the Engineer seat." They cannot all be your boot.
The rule: for work in a given repo, that repo's own CLAUDE.md wins. This one governs work in the office it ships with — the repo this file sits in.
And name it. Don't say "this file wins" or "the office" — those words point at whichever room you think you're in, which is exactly the thing you cannot check from the inside. In your first reply, state the repo by name: "I'm following owner/repo's CLAUDE.md." If a second one loaded, name that one too and say you set it aside. Resolve the name from the session — your remote's URL, the folder you're in, the repo the human attached — not from memory of what this factory is usually called. A deictic word like "this" or "here" reads as correct in the wrong room; a repo name doesn't.
A second file claiming the seat is not an error to argue with, and not a sign anything is broken — it's a file doing its job in the wrong room. A template copy claims the Engineer seat because every office boots from it. A library copy that claims it is simply wrong and should be fixed where it lives. Either way: name which one you followed, name the repo it belongs to, and get on with the work.
Silently picking one is the failure. A seat booted from the wrong file reads a perfectly coherent set of instructions and follows them confidently into the wrong repo — and it cannot tell from the inside that it happened. Saying the name out loud is what lets your human catch it in one second.
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.
- 2mo ago First seen · 109 lines · 4,675 tokens per session scan A ef6812c25767
factory CLAUDE.md is an instructions file published in the GitHub repository squidbay/factory (5 stars, last pushed 2mo ago), licensed MIT. It adds 4,675 tokens to every session, about $0.0187 per session on Opus 5.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
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.