You can demo an agent in an afternoon.
You can regret it in six months.
Prompts live in chat history. Rules are copy-pasted across five tools. MCP servers sprawl without contracts. Skills exist but nobody knows which agent loads them. “Vibe coding” ships until the repository becomes unnavigable for humans and machines.
That is not a model problem first.
That is agentic repo debt.
The Agentic Codebase names the disease and installs the cure.
The thesis that cuts through tool noise
Agents do not fail only because models are weak.
They fail because repositories, rules, and tool contracts were never designed for machine collaborators.
So stop treating the agent surface as disposable chat.
Version the agent OS like you version the app.
STACK: five layers, one maintainable system
STACK is the architecture:
- Structure — the repo tree agents and humans can both navigate.
- Toolchain — shells, runners, and deterministic workflows that do not rot.
- Agent configuration — AGENTS.md / CLAUDE.md, rules, skills, roles, and charters that agree.
- Connection layer — MCP and integrations with contracts, not hope.
- Knowledge and quality — memory, evals, hooks, CI gates, and regression discipline.
Five layers.
One operating system for agent work.
What you can ship after reading
Not vibes. Artifacts.
- a coherent agent instruction surface across tools
- skill packages that are discoverable and owned
- MCP tool contracts that fail closed when wrong
- hooks and evals that catch regressions before users do
- a STACK audit you can run on a brownfield repo this week
This is software engineering applied to the agent instruction plane.
Who this book is for
- the staff engineer whose team uses Claude Code three incompatible ways
- the founder shipping agent features into a real product
- the platform lead standardizing AI coding practice
- the maintainer who inherited
CLAUDE.md,.cursorrules, andAGENTS.mdthat disagree - the operator who already read the strategy book and now needs the implementation layer
If you want a one-tool tour, this will feel rigid.
If you want production survival, that rigidity is the product.
Series context without soft cross-sell fog
- AI Agents for Startup Strategy answers where agents earn a place.
- The Agentic Author shows gated production for knowledge work.
- The Agentic Codebase hardens the repository those agents live in.
Different layer. Same seriousness.
Buy the edition your team will actually use
English editions (Amazon.com)
| Format | Link |
|---|---|
| Kindle | Buy English Kindle |
| Paperback | Buy English paperback |
| Hardcover | Buy English hardcover |
Dutch editions (Amazon.nl)
| Format | Link |
|---|---|
| Kindle | Koop Nederlandse Kindle |
| Paperback | Koop Nederlandse paperback |
| Hardcover | Koop Nederlandse hardcover |
Dutch page: boeken/the-agentic-codebase.
Close the loop
Vibe coding is real.
Without a lane, it is a path to repo rot.
Name the lane. Instrument the gate. Keep the agent OS versioned.