Borrowing it
Nothing to install: this file belongs to neon-solutions/add-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/neon-solutions/add-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/neon-solutions/add-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/neon-solutions/add-mcp/agents-md)<a href="https://agentmods.dev/instructions/neon-solutions/add-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/neon-solutions/add-mcp/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.00629 | $0.00629 |
| Opus 5 | $0.00315 | $0.00315 |
| Sonnet 5 | $0.00126 | $0.00126 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
add-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 6d 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 — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
add-mcp
A CLI to install MCP servers for different coding agents (Claude Code, Cursor, VS Code, OpenCode, Codex, Grok Build) with a single command.
Dev environment
- Use bun as package manager and to run package.json scripts
- Fallow is a local dev dependency (
bun run fallow). It reports unused code, duplication, and complexity across the repo; fix what matters locally and ignore noise when appropriate. It does not run in GitHub Actions.
Changelog
CHANGELOG.md is for user-facing changes only: new features and bug fixes that affect people using the CLI. Skip internal-only work (tooling, CI, dev dependencies, refactors with no behavior change). When you ship something that belongs in the changelog, add an entry in the same tone as existing ones and bump package.json per semver—often one entry + bump per release batch.
Dev and PR workflow
- Branch from up-to-date
main—git checkout main && git pull. - Implement the change — keep the diff focused; match existing style and patterns.
- Tests — add or extend tests so behavior and edge cases are covered by the spec. Prefer unit tests without mocks and e2e tests without mocks (this repo’s style).
- Typecheck —
bun run typecheck; fix all reported issues. - Tests —
bun run test; fix failures. - Quality pass — run
bun run fmt, thenbun run build,bun run typecheck, andbun run testagain so formatting, build, types, and tests are all green. - Fallow —
bun run fallow(orbun run fallow -- --summary). Address findings that are clearly worth it; not every Fallow warning needs a code change. - Release notes — if the change is user-facing (feature or bug fix), add a short
CHANGELOG.mdentry and bumppackage.jsonper semver; otherwise skip the changelog. - README — update only if end users need to know about a new or changed feature.
- PR — push your branch and open a pull request against
main.
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.
- 6d ago First seen · 32 lines · 629 tokens per session scan A 82bd4c6a4906
add-mcp AGENTS.md is an instructions file published in the GitHub repository neon-solutions/add-mcp (292 stars, last pushed 8d ago), licensed Apache-2.0. It adds 629 tokens to every session, about $0.0031 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
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.
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.