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/aave/aave-v4-sdk/agents-mdgit clone --depth 1 https://github.com/aave/aave-v4-sdkWrote 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/aave/aave-v4-sdk/agents-md)<a href="https://agentmods.dev/instructions/aave/aave-v4-sdk/agents-md"><img src="https://agentmods.dev/badge/instructions/aave/aave-v4-sdk/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.00679 | $0.00679 |
| Opus 5 | $0.00340 | $0.00340 |
| Sonnet 5 | $0.00136 | $0.00136 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
aave-v4-sdk 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Dev Environment
nvm use && corepack enable && pnpm install && pnpm build
Testing
pnpm test --run # All tests
pnpm test:<package> --run # Package: types, core, client, react, cli
pnpm vitest --run --project <project> <file> -t "<test-name>" # Specific test
SDK Architecture
| Package | Purpose |
|---|---|
@aave/graphql |
GraphQL queries, fragments, types |
@aave/client |
TypeScript client actions (imperative API) |
@aave/react |
React hooks (declarative API) |
@aave/types |
Shared TypeScript types |
@aave/core |
Core SDK functionality |
@aave/cli |
Command-line tools |
Key concepts:
- Actions (
packages/client/src/actions/): Imperative functions for GraphQL queries - Hooks (
packages/react/src/): React hooks wrapping actions with state management - Imperative read hooks (
use[X]Action): Usecache-firstpolicy, exceptusePreviewAction,useExchangeRateAction, and swap quote hooks which usenetwork-only
When updating GraphQL queries, update corresponding actions. Only update hooks if explicitly requested.
Schema Updates
Use Claude /schema-update skill. See .claude/skills/schema-update/SKILL.md.
Commits & Changesets
Commits: conventional format (fix:, feat:, chore:), no Co-Authored-By trailers.
Changesets: Create manually in .changeset/ (e.g., adjective-noun-verb.md):
---
"@aave/graphql": patch
"@aave/client": patch
"@aave/react": patch
---
**fix:** description using `backticks` for code references
patch= bug fix,minor= feature,major= breaking change- Always include
@aave/clientand@aave/reactwhen changing their dependencies (@aave/graphql,@aave/types,@aave/core) - One-line description only, bold type prefix (
**fix:**)
Snapshot Releases
Snapshot releases publish packages for testing without updating the real versions. They are triggered manually.
Published versions follow the format 0.0.0-<tag>-<timestamp> (e.g. 0.0.0-snapshot-20260427120000).
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 · 75 lines · 679 tokens per session scan A 99e5f91b1974
aave-v4-sdk AGENTS.md is an instructions file published in the GitHub repository aave/aave-v4-sdk (24 stars, last pushed 2d ago), licensed MIT. It adds 679 tokens to every session, about $0.0034 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.