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/jokull/agent-cms/agents-mdgit clone --depth 1 https://github.com/jokull/agent-cmsWhat 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.00717 | $0.00717 |
| Opus 5 | $0.00358 | $0.00358 |
| Sonnet 5 | $0.00143 | $0.00143 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
agent-cms 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 yesterday.
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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — agent-cms
For agents working on this codebase (not consuming the CMS).
Project structure
src/mcp/— MCP server: tools, resources, promptssrc/graphql/— GraphQL schema builder and resolvers (read-only content delivery)src/services/— business logic (model, field, record, publish, asset, webhook, schema-io)src/db/— row types, validator accessorssrc/field-types.ts— field type registry with validation schemassrc/dast/— DAST (structured text) validation and traversalsrc/search/— FTS5 + Vectorize searchsrc/schema-engine/— DDL generation for content tablessrc/http/— REST API routessrc/index.ts— Cloudflare Worker entry point, layer composition
Architecture
Effect services with SqlClient dependency injection. Layers composed at the entry point:
D1Client.layer→SqlClient.SqlClientVectorizeContext→ optional AI/Vectorize bindingsLayer.merge(sqlLayer, vectorizeLayer)→ provided once at handler boundaryEffect.runPromiseonly at framework boundaries (MCP, GraphQL Yoga, HTTP handler)
See docs/contributing/effect.md for full patterns.
Conventions
- No
ascasts — use Effect Schema or runtime checks - No
any— use row types fromsrc/db/row-types.tsorunknown - Errors are
Data.TaggedErrorinsrc/errors.ts - Field api_keys are snake_case; GraphQL maps to camelCase/PascalCase at the resolver layer
Testing
npx vitest run # all tests
npx vitest run test/mcp # scoped to MCP tests
Test helpers in test/app-helpers.ts — creates in-memory D1, runs migrations, provides run() for Effect.
How to add things
New field type: Add to src/field-types.ts registry (column type, default, validation schema). Update src/graphql/schema-builder.ts for GraphQL type mapping.
New MCP tool: Add server.tool(name, description, zodSchema, async (args) => run(Service.method(args))) in src/mcp/server.ts. Keep tools thin — logic goes in services.
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.
- yesterday First seen · 68 lines · 717 tokens per session scan A af1ac86a51e6
agent-cms AGENTS.md is an instructions file published in the GitHub repository jokull/agent-cms (4 stars, last pushed 8d ago), licensed MIT. It adds 717 tokens to every session, about $0.0036 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
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.
buildNext
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
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit 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.
langchain 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.