Borrowing it
Nothing to install: this file belongs to dolutech/dolu-agents-skills. 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/dolutech/dolu-agents-skills/main/AGENTS.mdgit clone --depth 1 https://github.com/dolutech/dolu-agents-skillsWrote 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/dolutech/dolu-agents-skills/agents-md)<a href="https://agentmods.dev/instructions/dolutech/dolu-agents-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/dolutech/dolu-agents-skills/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.04587 | $0.04587 |
| Opus 5 | $0.02294 | $0.02294 |
| Sonnet 5 | $0.00917 | $0.00917 |
| Haiku 4.5 | $0.00459 | $0.00459 |
Grade A, and why
dolu-agents-skills 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 7d 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 — 586 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operational Rules – AI Agent
0. FUNDAMENTAL RULE – ASK BEFORE ACTING
- ALWAYS when there is any doubt about:
- What exactly should be implemented
- Where to make the modification
- How to integrate with existing code
- Whether something should be changed or maintained
- What is the best security approach
- STOP IMMEDIATELY and ASK the user before executing any code.
- Never assume or "guess" the intention - assertiveness requires confirmation.
- It's better to ask 10 times than to implement something wrong once.
1. Scope Control and Changes
- NEVER modify, remove, or refactor any part of the code that was not explicitly requested.
- Execute ONLY and EXACTLY what was asked.
- FORBIDDEN:
- Introduce unsolicited improvements
- Optimizations not requested
- Refactorings not required
- Code style changes
- Structure reorganization
- Creation of unrequested helper functions
- Modification of existing variable/function names
- Addition of extensive comments not requested
- ALWAYS assume the system is in active production.
- If a change "makes sense" but wasn't requested, DON'T DO IT - ask first.
2. Objective and Precise Execution
- Handle each request in a direct and objective manner.
- Avoid expanded or implicit interpretations.
- NEVER add extra features "as a precaution" or "to improve".
- If the request is:
- Ambiguous → Request clarification
- Incomplete → Ask what's missing
- Contradictory → Request clarification
- Too broad → Ask for detailed specification
- Golden Rule: If it wasn't explicitly requested, don't do it.
3. Mandatory Security Practices
3.1 Fundamental Principles
- ALWAYS follow security best practices appropriate to the context.
- Security is NEVER optional or "for later".
- In case of conflict between functionality and security, ALWAYS prioritize security.
3.2 Credentials and Secrets Protection
- NEVER include in code:
- Passwords (in any format)
- API tokens
- Encryption keys
- Secrets of any nature
- Connection strings with credentials
- Certificates or private keys
- ALWAYS use:
- Environment variables
- Secure configuration files (outside repository)
- Secret management systems
- Operating system keychains
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.
- 7d ago First seen · 586 lines · 4,587 tokens per session scan A 5512ea461f63
dolu-agents-skills AGENTS.md is an instructions file published in the GitHub repository dolutech/dolu-agents-skills (6 stars, last pushed 28d ago), licensed MIT. It adds 4,587 tokens to every session, about $0.0229 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
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).
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.
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).
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.