Borrowing it
Nothing to install: this file belongs to easyhooon/dari. 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/easyhooon/dari/main/AGENTS.mdgit clone --depth 1 https://github.com/easyhooon/dariWrote 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/easyhooon/dari/agents-md)<a href="https://agentmods.dev/instructions/easyhooon/dari/agents-md"><img src="https://agentmods.dev/badge/instructions/easyhooon/dari/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/easyhooon/dari/agents-md"><img src="https://agentmods.dev/badge/instructions/easyhooon/dari/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.00468 | $0.00468 |
| Opus 5.5 | $0.00187 | $0.00187 |
| Sonnet 5.5 | $0.00094 | $0.00094 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
dari 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 3d 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Guidelines
Commit & PR Rules
- Do NOT include
Co-Authored-Bylines referencing Codex in commit messages. - Do NOT include "Generated with Codex" or similar AI attribution in PR descriptions.
- Do NOT use a
codex/branch prefix. Follow the existing type-based convention, such asfeat/,fix/,chore/,docs/, orrefactor/. - Keep commit messages compact. Subject ≤ 72 chars. Body only when the "why" isn't obvious from the diff — 1–3 short lines, no multi-paragraph essays. Don't restate what the diff already shows.
- Write commit subjects and bodies in English. Write PR titles in English too. Keep code, documentation, quoted user content, and existing history in their original language.
Code Style
- Do NOT use fully-qualified names (FQN) inline in Kotlin code. Always add a proper
importstatement at the top of the file and reference the type by its simple name. This applies to both production and test code. - Keep comments compact. Explain non-obvious intent in one or two lines. No multi-paragraph KDoc unless the API is genuinely complex. Skip comments that just restate the code.
Code Style
- Do NOT use fully-qualified names (FQN) inline in Kotlin code. Always add a proper
importstatement at the top of the file and reference the type by its simple name. This applies to both production and test code.
Issues
- Write all issues in English.
- Use clear section headers:
## Summary,## Problem/## Motivation,## Proposed Approach/## Proposed Behavior, etc. - Include relevant code snippets, color values, or architecture details where helpful.
Release
- Always run
./gradlew cleanbeforepublishAllPublicationsToMavenCentralRepositoryto ensure freshly compiled artifacts are uploaded (not stale build cache).
Skills
- Code review follow-up: use the
/resolve-coderabbit-reviewskill to triage and apply CodeRabbit comments on the current PR. - Release: use the
/releaseskill to publish to Maven Central and draft GitHub release notes.
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.
- 3d ago First seen · 34 lines · 468 tokens per session scan A db991258faff
dari AGENTS.md is an instructions file published in the GitHub repository easyhooon/dari (38 stars, last pushed today), licensed Apache-2.0. It adds 468 tokens to every session, about $0.0019 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-10-26.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.