Borrowing it
Nothing to install: this file belongs to davisjam/model-based-agentic-software-engineering. 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/davisjam/model-based-agentic-software-engineering/main/CLAUDE.mdgit clone --depth 1 https://github.com/davisjam/model-based-agentic-software-engineeringWrote 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/davisjam/model-based-agentic-software-engineering/claude-md)<a href="https://agentmods.dev/instructions/davisjam/model-based-agentic-software-engineering/claude-md"><img src="https://agentmods.dev/badge/instructions/davisjam/model-based-agentic-software-engineering/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/davisjam/model-based-agentic-software-engineering/claude-md"><img src="https://agentmods.dev/badge/instructions/davisjam/model-based-agentic-software-engineering/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.18871 | $0.18871 |
| Opus 5.5 | $0.07548 | $0.07548 |
| Sonnet 5.5 | $0.03774 | $0.03774 |
| Haiku 4.5 | $0.01887 | $0.01887 |
Grade A, and why
model-based-agentic-software-engineering CLAUDE.md scanned grade A 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl -s .../actions/runs?per_page=3` gives `head_sha` / `status` / `conclusion`, and How it starts
The opening of the file, as written. The whole thing — 884 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — agent-governance-mechanisms
This repo is a pattern catalogue: 85 governance mechanisms that keep a fleet of autonomous coding agents productive while bounding their failures, each written as a Gang-of-Four-style design pattern. It is published as a static GitHub Pages site and embedded in a parent repo as a git submodule.
catalog.py is the one tool — stdlib-only, no dependencies (so python3 catalog.py … runs on a
fresh checkout with nothing installed). Do not add pip dependencies; keep it clone-and-run.
Site is a preview; the book claims and expands
The published site — the landing, the catalogue views, the entry pages — is a preview: concise
framings and entry points. The book (under book/) is where each idea is claimed and expanded.
Two jobs, one for each surface.
The standing implication: book coverage ⊇ site framings. Any conceptual framing that appears on the
site should have a fuller treatment in the book. When you add a framing to the site's landing prose (the
LANDING_INTRO, the schools, the ways, the spectrum axis) or an entry page, either the book already
expands it or you owe it a home there. Site-only material is limited to adoption and navigation —
DIY-vs-install, the nav cards, the quick-start; those need no book counterpart. Everything conceptual does.
What is a mechanism?
A mechanism is a recurring, failure-killing pattern of governance — written like a Gang-of-Four design pattern: the failure class it prevents, the shape that prevents it, and why it is not just the cheaper thing everyone already does. A mechanism earns its own entry only when it clears three bars:
- It kills a failure class, not a one-off bug. If you can't name the recurring failure, it isn't a mechanism yet.
- It's distinct. It does something the naive or adjacent alternative can't — every entry must survive its own "Why it's not just [X]" section. Two entries built on the same pattern are distinct only when they vary a named axis (lock cardinality, object model, enforcement scope, domain); if nothing varies, merge them.
- Its examples instantiate it. Every example — in Motivation, in "Why it's not just…", in Known uses — must be a real case of this mechanism, not a sibling's. (A relational config-field ⊆ sample check is a coherence lint, not a per-source semantic lint — so cite it under coherence only.) An example borrowed from a neighbour blurs the exact boundary the catalogue exists to draw.
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.
- today Changed · +12 lines · +287 tokens per session f0f6f951d7e9
- 2d ago Changed · +74 lines · +1,743 tokens per session 43a225563a91
- 3d ago Changed · +12 lines · +276 tokens per session a618c155b745
- 9d ago Changed · +45 lines · +874 tokens per session 8169ef095743
- 10d ago Changed · +198 lines · +4,233 tokens per session 1b4b4f8c477c
- 11d ago Changed · +79 lines · +1,818 tokens per session 4e7497984da1
- 12d ago Changed · +56 lines · +1,277 tokens per session 8e3b9ea8a869
- 13d ago Changed · +134 lines · +2,988 tokens per session e734a9bc4bb0
- 15d ago Changed · +40 lines · +940 tokens per session 165669d008a7
- 16d ago First seen · 234 lines · 4,435 tokens per session scan A 0421f80aee82
model-based-agentic-software-engineering CLAUDE.md is an instructions file published in the GitHub repository davisjam/model-based-agentic-software-engineering (25 stars, last pushed yesterday), licensed MIT. It adds 18,871 tokens to every session, about $0.0755 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
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).