Borrowing it
Nothing to install: this file belongs to desplega-ai/agent-fs. 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/desplega-ai/agent-fs/main/CLAUDE.mdgit clone --depth 1 https://github.com/desplega-ai/agent-fsWrote 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/desplega-ai/agent-fs/claude-md)<a href="https://agentmods.dev/instructions/desplega-ai/agent-fs/claude-md"><img src="https://agentmods.dev/badge/instructions/desplega-ai/agent-fs/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.02346 | $0.02346 |
| Opus 5 | $0.01173 | $0.01173 |
| Sonnet 5 | $0.00469 | $0.00469 |
| Haiku 4.5 | $0.00235 | $0.00235 |
Grade A, and why
agent-fs 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 2d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-fs
See PRODUCT.md for product vision and positioning (agent-fs is to files what agentmail is to email).
Bun monorepo: packages/{core, cli, mcp, server}
Commands
bun install— install dependenciesbun run typecheck— TypeScript type checking (tsc --build)bun run build— bundle CLI for npm topackages/cli/dist/cli.jsbun run test— run tests (manual/integration tests auto-skip without env)bun run scripts/e2e.ts "bun run packages/cli/src/index.ts --"— CLI E2E tests (requires Docker for MinIO)bun run scripts/e2e.ts "bun run packages/cli/src/index.ts --" --local-only— credential-free local-filesystem E2E mode used in CI
Releasing & Deployment
RELEASING.md is the source of truth for the release process — read it before touching versions, release scripts, or the publish workflows. Do not restate its mechanics elsewhere; link to it.
See DEPLOYMENT.md for deployment targets (npm package contents, Docker/GHCR, Fly.io, env vars).
Short version: releases are automatic. A version change landing on main triggers tag + publish.
./scripts/release.sh 0.13.0 # sync every version target, commit, push
Never bump a version by hand-editing package.json — scripts/sync-versions.ts owns every place the version appears, and CI fails a partial bump.
Two more invariants that sync-versions.ts --check enforces on every PR and before every tag (details in RELEASING.md § Version targets): bun.lock workspace versions move with the release version, and the bun version is pinned to the same exact number in package.json packageManager, both Dockerfile FROM oven/bun: tags, and every workflow bun-version:. Never use a floating oven/bun:1.4 tag. Bump the three places together, and run bun install --frozen-lockfile after any dependency or version change so the lockfile is committed with it.
Release Checklist (applies to plans, research, and Plan mode)
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.
- 2d ago Changed · +2 lines · +147 tokens per session 23ee83160027
- 8d ago First seen · 100 lines · 2,199 tokens per session scan A b5064a0592b8
agent-fs CLAUDE.md is an instructions file published in the GitHub repository desplega-ai/agent-fs (15 stars, last pushed today), licensed MIT. It adds 2,346 tokens to every session, about $0.0117 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.
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.
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.
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 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).
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.