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/evefrontier/dapp-index/agents-mdgit clone --depth 1 https://github.com/evefrontier/dapp-indexWrote 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/evefrontier/dapp-index/agents-md)<a href="https://agentmods.dev/instructions/evefrontier/dapp-index/agents-md"><img src="https://agentmods.dev/badge/instructions/evefrontier/dapp-index/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.00887 | $0.00887 |
| Opus 5 | $0.00443 | $0.00443 |
| Sonnet 5 | $0.00177 | $0.00177 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
dapp-index 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dapp Index Agent Guide
Tool Compatibility
- This file is the canonical shared instruction source for AI coding agents.
- Codex reads
AGENTS.mddirectly. - GitHub Copilot can use
AGENTS.md;.github/copilot-instructions.mdalso points Copilot chat/review surfaces back to this file. - Claude Code reads
CLAUDE.md, which imports this file. - Gemini CLI reads
GEMINI.md, which imports this file. - Cursor reads
.cursor/rules/dapp-index.mdc, which points back to this file and repeats the highest-priority rules. - Windsurf reads
AGENTS.mddirectly through its rules engine. - Keep tool-specific behavior in adapter files or workflow prompts instead of duplicating full instructions.
Project Shape
- This repo owns the Dapp Index web app, Sui Move registry package, builder metadata schema, Walrus metadata flow, and index governance docs.
- Keep Move, Walrus metadata, MVR verification, frontend UI, and docs changes reviewable as separate surfaces.
- Prefer small branches from
main. This workspace uses thecodex/prefix for Codex-generated branches.
Working Rules
- Protect user work. Never revert unrelated changes or run destructive git commands unless explicitly asked.
- Read the relevant docs before changing architecture:
README.md,docs/BUILDER_PLAN.md, and any scopedAGENTS.md. - Use existing repo patterns before adding abstractions or dependencies.
- Ask before adding production dependencies, new services, or automatic deploy/publish behavior.
- Sui package publishing, mainnet-facing release steps, and wallet-funded transactions stay manual unless the user explicitly asks otherwise.
PR discipline
Optimize for reviewability over delivery speed. A PR should answer one clear question: what behavior or contract changed, and can a reviewer verify that in isolation?
Scope
- One concern per PR. Separate Move, metadata/schema, frontend, Walrus flow, and docs unless the change is trivially coupled.
- Prefer small diffs. If a change spans multiple layers or surfaces, treat that as a signal to split or stack rather than as normal.
- Stack PRs only when dependency is real. Land foundations before consumers: public contract → persistence → domain logic → UI.
- Do not attach unrelated fixes to an in-flight feature branch because it is convenient.
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 · 69 lines · 887 tokens per session scan A 5a8e4838d551
dapp-index AGENTS.md is an instructions file published in the GitHub repository evefrontier/dapp-index (5 stars, last pushed today), licensed MIT. It adds 887 tokens to every session, about $0.0044 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
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.