Borrowing it
Nothing to install: this file belongs to ben-vargas/ai-sdk-provider-claude-code. 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/ben-vargas/ai-sdk-provider-claude-code/main/AGENTS.mdgit clone --depth 1 https://github.com/ben-vargas/ai-sdk-provider-claude-codeWrote 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/ben-vargas/ai-sdk-provider-claude-code/agents-md)<a href="https://agentmods.dev/instructions/ben-vargas/ai-sdk-provider-claude-code/agents-md"><img src="https://agentmods.dev/badge/instructions/ben-vargas/ai-sdk-provider-claude-code/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.1 | $0.00585 | $0.00585 |
| Opus 5 | $0.00293 | $0.00293 |
| Sonnet 5 | $0.00117 | $0.00117 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
ai-sdk-provider-claude-code 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 7d 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
- Provider code and utilities sit in
src/; each module keeps a matching*.test.ts(for example,src/claude-code-provider.ts). - Executable samples live in
examples/; rebuild first, then run withnpx tsx ...to exercise streaming or tool flows. - Long-form docs and migration notes are under
docs/ai-sdk-v5/anddocs/ai-sdk-v4/; touch both when behavior diverges, and ignore generateddist/artifacts.
Build, Test, and Development Commands
npm run build→tsupbuild for CJS/ESM bundles.npm run dev→ watch mode for rapid iterations.npm run lint/npm run typecheck→ ESLint plustsc --noEmitto keep APIs strict.npm run test(or:node/:edge) → Vitest suites per runtime; includenpm run test:integrationbefore publishing.npm run example:streaming(orrun-all-examples.sh) → smoke-test streaming tools described inTOOL_STREAMING.md.
Coding Style & Naming Conventions
- 2-space indentation,
constfirst, and no implicitany; ESLint enforces the ruleset and only relaxes the constraint inside tests. - File names stay kebab-case, exports are named, and TypeScript types/interfaces remain PascalCase.
- Factor shared behaviors into helpers like
mcp-helpers.tsorlogger.tsinstead of duplicating logic.
Testing Guidelines
- Keep tests beside the module (
foo.ts↔foo.test.ts) and mirror the API surface you touch. - Exercise Node and edge shim paths with
npm run test:nodeandnpm run test:edge; add scenario coverage inexamples/when reproducing tool or streaming regressions. - Run
npx vitest run --coverage(V8) before tagging a release and address drops introduced by new branches.
Commit & Pull Request Guidelines
- Use conventional commits (
feat:,fix(scope):,chore:) as in the log; reserve breaking changes for the body with a clear callout. - Reference issues with
#NN, list the commands you ran, and include relevant screenshots or CLI transcripts when workflows change. - Update companion docs (
README.md,TOOL_STREAMING.md,docs/ai-sdk-v5/GUIDE.md) in the same PR whenever behavior or configuration shifts.
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.
- 7d ago First seen · 38 lines · 585 tokens per session scan A d3d0022db656
ai-sdk-provider-claude-code AGENTS.md is an instructions file published in the GitHub repository ben-vargas/ai-sdk-provider-claude-code (365 stars, last pushed 6d ago), licensed MIT. It adds 585 tokens to every session, about $0.0029 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
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.
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.
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).
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.