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/contentful/contentful-resolve-response/agents-mdgit clone --depth 1 https://github.com/contentful/contentful-resolve-responseWrote 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/contentful/contentful-resolve-response/agents-md)<a href="https://agentmods.dev/instructions/contentful/contentful-resolve-response/agents-md"><img src="https://agentmods.dev/badge/instructions/contentful/contentful-resolve-response/agents-md.svg" alt="Measured on agentmods" 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 | $0.00666 | $0.00666 |
| Opus 5 | $0.00333 | $0.00333 |
| Sonnet 5 | $0.00133 | $0.00133 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
contentful-resolve-response 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 4d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guide
Read this file first. It tells you where to find context in this repo.
Quick Reference
| What you need | Where to look |
|---|---|
| How this repo is structured | ARCHITECTURE.md |
| How to build/test/run | CONTRIBUTING.md |
| Why decisions were made | docs/ADRs/ |
| What this repo does | README.md |
| PR review rules | .bito/guidelines/ |
| Active specs/work | docs/specs/ |
Sharp Edges & Invariants
- Single-file library — All implementation lives in
index.js. There is nosrc/directory or multi-file architecture. Do not split into multiple files without an ADR. - Input immutability contract — The library deep-copies input via
fast-copybefore mutation. Never remove or bypass this copy step; consumers rely on their input being unmodified. - UNRESOLVED_LINK sentinel — Uses a unique empty object (
{}) as a sentinel, notnull/undefined/Symbol. Do not change this pattern; it avoids polyfill bloat and is used for identity comparison. - ResourceLink provider check — Only
Contentful:prefixed resource links are resolved. Unknown providers must be passed through unchanged, never removed. - No TypeScript — Source is plain JavaScript (ES modules via Babel). Do not add TypeScript without consensus.
- dist/ is generated — Never edit files in
dist/. Always runnpm run buildto regenerate. - CHANGELOG.md is generated — Managed by semantic-release. Never edit manually.
- Conventional Commits required — Commitlint enforces conventional commit format. Non-conforming commits will be rejected by the pre-commit hook.
Key Conventions
- Commit format: Conventional Commits enforced by
commitlint+ Husky pre-commit hook - Branch strategy:
master(production) + feature branches;betaanddevfor pre-releases - Test location:
test/unit/with Mocha + Chai - Module system: Dual CJS + ESM (source is ESM, Babel outputs both)
- Formatting: Prettier (120 chars, no semicolons, single quotes)
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.
- 4d ago First seen · 52 lines · 666 tokens per session scan A 32f9c59d9a60
contentful-resolve-response AGENTS.md is an instructions file published in the GitHub repository contentful/contentful-resolve-response (57 stars, last pushed 24d ago), licensed MIT. It adds 666 tokens to every session, about $0.0033 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-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).
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.
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.