Borrowing it
Nothing to install: this file belongs to elephant-xyz/elephant-mcp. 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/elephant-xyz/elephant-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/elephant-xyz/elephant-mcpWrote 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/elephant-xyz/elephant-mcp/agents-md)<a href="https://agentmods.dev/instructions/elephant-xyz/elephant-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/elephant-xyz/elephant-mcp/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/elephant-xyz/elephant-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/elephant-xyz/elephant-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00711 | $0.00711 |
| Opus 5 | $0.00356 | $0.00356 |
| Sonnet 5 | $0.00142 | $0.00142 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
elephant-mcp 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 9d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
Core server code lives in src/. src/index.ts hosts the MCP Express server, src/config.ts normalizes environment variables, src/logger.ts wires Pino logging, and src/lib/ contains reusable helpers alongside colocated tests such as utils.test.ts. Build artifacts land in dist/; configuration files (vite.config.ts, tsconfig.json, eslint.config.js) sit at the repository root.
Build, Test, and Development Commands
Use npm run dev for a live TypeScript dev loop with native type stripping (enabled by default in Node.js 22.18+). npm run build compiles to ES modules via Vite, while npm start serves the compiled output from dist/. Run npm run test for the interactive Vitest runner or npm run test:ci to emit JSON results into test-results.json. Quality gates include npm run lint, npm run lint:fix, npm run format, and npm run format:check.
Coding Style & Naming Conventions
TypeScript files use ES module syntax (import/export) and live under src/. Follow the default Prettier style (two-space indent, double quotes, trailing commas) enforced by the formatting scripts. ESLint runs with @typescript-eslint; unused variables must be prefixed with _ if intentional, and any is discouraged. Prefer camelCase for functions and variables, PascalCase for types, and descriptive filenames like logger.ts or utils.ts.
Testing Guidelines
Vitest powers unit tests. Name specs *.test.ts and keep them beside the code under test to mirror the existing src/lib/utils.test.ts pattern. Cover new tools, transports, and configuration logic with focused tests that exercise observable behaviour. Failing tests should reproduce regressions before fixes; wrap asynchronous tests with async/await to keep stack traces actionable.
Commit & Pull Request Guidelines
Adopt Conventional Commits (feat:, chore:, docs:) as seen in the history to keep change logs readable. Each PR should summarize the user-facing impact, reference related issues, and list follow-up tasks if scope is deferred. Include testing evidence (npm run test, npm run lint) and call out new environment variables or configuration knobs so reviewers can verify runtime changes.
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.
- 9d ago First seen · 37 lines · 711 tokens per session scan A 9bb45a9e938d
elephant-mcp AGENTS.md is an instructions file published in the GitHub repository elephant-xyz/elephant-mcp (2 stars, last pushed yesterday), licensed MIT. It adds 711 tokens to every session, about $0.0036 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
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.
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).
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.