Borrowing it
Nothing to install: this file belongs to pavel-molyanov/molyanov-ai-dev. 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/pavel-molyanov/molyanov-ai-dev/main/AGENTS.mdgit clone --depth 1 https://github.com/pavel-molyanov/molyanov-ai-devWrote 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/pavel-molyanov/molyanov-ai-dev/agents-md)<a href="https://agentmods.dev/instructions/pavel-molyanov/molyanov-ai-dev/agents-md"><img src="https://agentmods.dev/badge/instructions/pavel-molyanov/molyanov-ai-dev/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/pavel-molyanov/molyanov-ai-dev/agents-md"><img src="https://agentmods.dev/badge/instructions/pavel-molyanov/molyanov-ai-dev/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.00382 | $0.00382 |
| Opus 5.5 | $0.00153 | $0.00153 |
| Sonnet 5.5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
molyanov-ai-dev 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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- molyanov-ai-dev CLAUDE.md — 94% identical, 6 lines differ
What it actually says
Language
- Artifacts addressed to the user (chat, plans, plan-mode, interviews, validator summaries, user-spec, README): the language the user writes in. Declare your language here — e.g. "This user writes in English." Skills and agents read the user's language from this line.
- Technical docs, code, code comments, AI prompts, internal logs (tech-spec, tasks, AGENTS.md, skills): English.
Behavior
- No "Great question!", no filler, no water.
- NEVER use request_user_input tool. Ask questions as plain text in chat instead.
- Never create Git worktrees or extra project copies unless the user explicitly asks.
Task Scope
- The user's request and any explicitly approved plan define the authorized scope of work.
- Choose the minimal solution sufficient for the task. Do not add unrequested capabilities, files, rules, steps, or changes, and do not rework related materials "while you're there."
- Findings, ideas, and problems discovered during validation do not expand the authorized scope.
- Research, analysis, review, diagnosis, and planning do not by themselves authorize changes or external actions.
Task Planning
- Use update_plan for multi-step tasks (>1 step).
- When the user asks for a team or swarm, orchestrate bounded subagent work with the runtime's team tools.
Security
- NEVER ask user to write secrets in chat
- Instead: provide instructions where to store them securely
- Local:
.envfiles, config files - CI/CD: GitHub Actions secrets
- Local:
- ALWAYS ask before pushing to main
- ALWAYS add secrets to
.gitignore:.env,*.key,credentials.json,secrets/ - Be cautious with external actions (push, deploy, send messages, create PRs). Ask before acting externally when uncertain.
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.
- 10d ago Changed · +1 lines · +6 tokens per session 5db5966774b5
- 1mo ago First seen · 34 lines · 376 tokens per session scan A cf14ae423c36
molyanov-ai-dev AGENTS.md is an instructions file published in the GitHub repository pavel-molyanov/molyanov-ai-dev (300 stars, last pushed 6d ago), licensed MIT. It adds 382 tokens to every session, about $0.0015 per session on Opus 5.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
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.