Borrowing it
Nothing to install: this file belongs to n-r-w/yandex-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/n-r-w/yandex-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/n-r-w/yandex-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/n-r-w/yandex-mcp/agents-md)<a href="https://agentmods.dev/instructions/n-r-w/yandex-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/n-r-w/yandex-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/n-r-w/yandex-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/n-r-w/yandex-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.00555 | $0.00555 |
| Opus 5 | $0.00278 | $0.00278 |
| Sonnet 5 | $0.00111 | $0.00111 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
yandex-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 yesterday.
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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Specific Rules and Information
Project: Yandex MCP Server
NO BACKWARDS COMPATIBILITY! NO FALLBACK! NO DEPRECATIONS! JUST REMOVE OLD CODE/DOCUMENTATION AS NEEDED. THIS IS A NEW PROJECT, NOT IN PRODUCTION YET. NO DATA IN DATABASE YET. FEEL FREE TO MAKE BREAKING CHANGES AS NEEDED.
Tech stack
- go 1.27
github.com/modelcontextprotocol/go-sdkfor MCP server implementationgithub.com/stretchr/testifyfor testsgo.uber.org/mock(no custom mocks,//go:generate go tool mockgendirectives in interface files)github.com/caarlos0/env/v11for loading configuration from environment variableslog/slogfor logging (must use structured logging with context)
Instructions
- Generate new documentation in English unless user specifically requests another language.
- Maintain consistency of environment variables between
.env.example,.env, Taskfile.yml, scripts, code, and documentation. - Use
task fmt,task lint,task buildto check code before completing changes.
Golang rules
- Use
go.uber.org/mockfor mocks - Use
github.com/stretchr/testifyfor tests - All interfaces MUST be prefixed with uppercase
Iletter - For single package:
- All interfaces should be in file
interfaces.go - Main package struct and its constructor should be in
service.goorclient.go - All internal structs (except main service struct and DTOs) should be in models.go
- All DTO should be in dto.go (structs with tag
json,yaml, etc.) - All configuration related code should be in config.go (using
github.com/caarlos0/env/v11) - All internal errors should be in errors.go file
- All internal constants should be in const.go file
- All mock generation commands should be in
interfaces.go
- All interfaces should be in file
- Use following functions to log system errors: internal/adapters/token/errors.go:LogError, internal/domain/errors.go:LogError
- Use
t.Context()instead ofcontext.Background()in tests - ALL DTOs MUST be not exported.
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.
- yesterday Changed · -112 lines · -1,232 tokens per session fc4fea66856c
- 10d ago First seen · 154 lines · 1,787 tokens per session scan A f8024342348e
yandex-mcp AGENTS.md is an instructions file published in the GitHub repository n-r-w/yandex-mcp (14 stars, last pushed 2d ago), licensed MIT. It adds 555 tokens to every session, about $0.0028 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).
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.
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.