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/AGENTS.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/agents-md)<a href="https://agentmods.dev/instructions/davisjam/model-based-agentic-software-engineering/agents-md"><img src="https://agentmods.dev/badge/instructions/davisjam/model-based-agentic-software-engineering/agents-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/agents-md"><img src="https://agentmods.dev/badge/instructions/davisjam/model-based-agentic-software-engineering/agents-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.02202 | $0.02202 |
| Opus 5.5 | $0.00881 | $0.00881 |
| Sonnet 5.5 | $0.00440 | $0.00440 |
| Haiku 4.5 | $0.00220 | $0.00220 |
Grade A, and why
model-based-agentic-software-engineering AGENTS.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 1mo 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — running editorial folds on the MAGE book with a fleet
This file is the operational playbook for making large editorial changes to the book
(book/) with dispatched agents. It extends CLAUDE.md §"Working on this repo with a fleet"
(single-live-writer + parallel drafting), which you should read first. Where CLAUDE.md states
the rules, this file gives the worked process — the one that lands a multi-part copyedit pass
in one sitting without serializing on main and without a merge that fights 100 generated files.
The method has four patterns. Use them together: draft in parallel → fold in parallel worktrees → merge by source-checkout → resolve the model layer once at the end.
0. The one fact everything follows from
main has a single-live-writer rule for exactly one reason: the pre-commit hook rebuilds the
site and force-stages the regenerated .html + derived book-models/* on every commit, so two
agents committing to the same branch collide on those generated files. Everything else about the
book is deterministic from source. That single fact is what makes the patterns below safe:
- Two folds on separate worktree branches never collide (separate git indexes).
- Two folds touching disjoint source trees (different Parts / the appendices) never conflict on content — only on regenerated files, which you never merge, you rebuild.
- A PDF renders from the working tree, not from
HEAD— so you can build a review PDF from staged-but-uncommitted source.
1. Pattern — disjoint-worktree parallel folds
When several folds touch disjoint source trees (e.g. Part II prose, Part III prose, appendices),
run them concurrently in separate git worktrees instead of serially on main.
Setup, per fold:
git worktree add -b <fold>-fold <path> HEAD(branch from currentmain; put<path>in a scratch dir).- ★ Copy the drafts into the worktree.
book/_design/drafts/is gitignored, so a fresh worktree checkout does not contain the EDIT-MAP or the authored figures. Without this the agent has nothing to fold:cp -r book/_design/drafts/<effort>-<date> <worktree>/book/_design/drafts/(they stay untracked in the worktree — the hook never stages them). - Dispatch the fold agent with its CWD = the worktree and a brief that says: you are on branch
<fold>-fold, confirm withgit branch --show-current, do NOT touchmain, other folds run concurrently on disjoint trees — ignore them.
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.
- 1mo ago First seen · 144 lines · 2,202 tokens per session scan A dafbd893dd27
model-based-agentic-software-engineering AGENTS.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 2,202 tokens to every session, about $0.0088 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-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).