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.
npx agentmods add instructions/michaelcjoseph/agent-coding-setup/claude-mdgit clone --depth 1 https://github.com/michaelcjoseph/agent-coding-setupWhat 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 | $0.00978 | $0.00978 |
| Opus 5 | $0.00489 | $0.00489 |
| Sonnet 5 | $0.00196 | $0.00196 |
| Haiku 4.5 | $0.00098 | $0.00098 |
Grade A, and why
agent-coding-setup 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This repository is a template for dropping a consistent Claude Code setup into any new coding project — a set of review/test/docs agents, a /work skill that drives tasks through plan → implement → test → review → simplify, and a docs/projects/ scaffold for specs and task lists.
When this template is copied into a real project, replace this file with a project-specific CLAUDE.md. The agents and the /work skill read CLAUDE.md to pick up project conventions, so the more specific the real CLAUDE.md is, the better the agents behave.
Using This Template
- Copy the contents of this repo into the new project root (preserving
.claude/anddocs/). - Replace this
CLAUDE.mdwith one that documents the real project — see "What to put in the project's CLAUDE.md" below. - Replace the
README.mdwith the project's own. - Add real projects under
docs/projects/NN-name/usingdocs/projects/templates/as the starting point. - Delete this file's "Using This Template" and "What to put in the project's CLAUDE.md" sections once the project has its own content.
What to put in the project's CLAUDE.md
The agents and /work skill expect the real CLAUDE.md to cover:
- Project overview — one paragraph on what the project does.
- Architecture — major subsystems, how they fit together, entry points.
- Project structure — directory tree of the main source folder with short comments.
docs-syncupdates this automatically. - Language / stack — language, runtime, build system, test framework.
- Key conventions — import style, config access, logging, centralized wrappers (the project's equivalents of "all HTTP calls go through
src/http.ts"). Thecode-reviewerandarchitecture-reviewerenforce these. - Running — how to run, test, and build.
docs-synckeeps this synced with the project manifest. - Environment variables — list with short descriptions.
- Agents — table of agents in
.claude/agents/and what they do.docs-synckeeps this synced. - Skills — table of skills in
.claude/skills/and what they do. - Threat model / security notes — public vs private repo, sensitive assets, trust boundaries. The
security-auditorreads this.
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 First seen · 60 lines · 978 tokens per session scan A c1c7aeef1e3a
agent-coding-setup CLAUDE.md is an instructions file published in the GitHub repository michaelcjoseph/agent-coding-setup (2 stars, last pushed 4mo ago), licensed MIT. It adds 978 tokens to every session, about $0.0049 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
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.
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).
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.