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/solana-foundation/solana-developer-platform/agents-mdgit clone --depth 1 https://github.com/solana-foundation/solana-developer-platformWrote 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/solana-foundation/solana-developer-platform/agents-md)<a href="https://agentmods.dev/instructions/solana-foundation/solana-developer-platform/agents-md"><img src="https://agentmods.dev/badge/instructions/solana-foundation/solana-developer-platform/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.00902 | $0.00902 |
| Opus 5 | $0.00451 | $0.00451 |
| Sonnet 5 | $0.00180 | $0.00180 |
| Haiku 4.5 | $0.00090 | $0.00090 |
Grade A, and why
solana-developer-platform 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 3d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solana Developer Platform
This file is the canonical agent guide for this repository.
Repo layout
apps/sdp-api: Node.js API deployed to Cloud Run, OpenAPI source, route handlers, Postgres/Redis integrationsapps/sdp-web: dashboard applicationapps/sdp-docs: public documentation site and generated API referencepackages/sdp-types: shared runtime types and shared product constants
Source of truth
- Public API contract:
apps/sdp-api/src/openapi/** - Public docs navigation:
apps/sdp-docs/content/docs/meta.json - Generated API docs:
apps/sdp-docs/content/docs/reference/api/** - AI discovery resources:
apps/sdp-docs/public/llms.txtandapps/sdp-docs/public/llms-full.txt
Generated files
Do not hand-edit generated artifacts. Regenerate them with the owning script.
- OpenAPI JSON:
pnpm -C apps/sdp-api openapi:generate - API playground catalog:
pnpm generate:api-playground - API reference docs:
pnpm -C apps/sdp-docs generate:api - AI discovery resources:
pnpm -C apps/sdp-docs generate:ai
Public vs internal surfaces
Public docs and AI artifacts should mirror the supported public surface only.
- Public API families:
health,api-keys,wallets,projects,issuance,payments,policies,compliance,earn - Hidden/internal families stay out of public AI resources unless product policy changes:
rpc,admin,onboarding,auth,organizations,members
Preferred checks
- Docs integrity:
pnpm --filter sdp-docs check:links - Docs build:
pnpm --filter sdp-docs build - Module boundaries:
pnpm check:module-boundaries - API playground drift:
pnpm check:api-playground - API typecheck:
pnpm --filter @sdp/api typecheck - API tests:
pnpm --filter @sdp/api test - Full workspace typecheck:
pnpm typecheck
Implementation guidance
- Prefer reusing generated docs/OpenAPI metadata instead of duplicating route inventories by hand.
- Keep public URLs coherent with the shared site constants in
@sdp/types/site. - When changing docs URLs or discovery resources, update both the docs site and any product links that point at it.
- Update
docs/architecture/module-map.mdwithpnpm generate:module-map; do not edit it by hand.
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.
- 3d ago First seen · 67 lines · 902 tokens per session scan A 3e9a0dd69614
solana-developer-platform AGENTS.md is an instructions file published in the GitHub repository solana-foundation/solana-developer-platform (49 stars, last pushed 3d ago), licensed MIT. It adds 902 tokens to every session, about $0.0045 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
tevm CLAUDE.md
Claude Code instructions for evmts/tevm, covering tevm monorepo commands and style guide, project overview, forking implementation, json-rpc support and commands.
starknet-agentic CLAUDE.md
Instructions for keep-starknet-strange/starknet-agentic, covering starknet agentic -- development context, cairo, typescript, skills and git.
solidity-typescript-hardhat-template CLAUDE.md
Instructions for protokol/solidity-typescript-hardhat-template, covering claude.md — project instructions, project overview, key commands, solidity conventions and test conventions.
polkadot-apps CLAUDE.md
Instructions for paritytech/polkadot-apps, covering claude.md, quick reference, key conventions, descriptors and chain client.
aztec-starter AGENTS.md
Instructions for AztecProtocol/aztec-starter, covering repository guidelines for codex agents, setup, development, testing and simulate before send.
sdk CLAUDE.md
Claude Code instructions for zama-ai/sdk, a project described as: TypeScript SDK for confidential FHE smart contracts on Zama Protocol.