Borrowing it
Nothing to install: this file belongs to EastStarAI/sanad-agent. 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/EastStarAI/sanad-agent/main/AGENTS.mdgit clone --depth 1 https://github.com/EastStarAI/sanad-agentWrote 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/eaststarai/sanad-agent/agents-md)<a href="https://agentmods.dev/instructions/eaststarai/sanad-agent/agents-md"><img src="https://agentmods.dev/badge/instructions/eaststarai/sanad-agent/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.03115 | $0.03115 |
| Opus 5 | $0.01558 | $0.01558 |
| Sonnet 5 | $0.00623 | $0.00623 |
| Haiku 4.5 | $0.00312 | $0.00312 |
Grade A, and why
sanad-agent 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 8d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sanad Agent Repository Contract
Documentation is the core constraint of this project. Treat /AGENTS.md (this file) as the Master Runtime Contract and bootloader for AI agents and human developers working on the open-source components of the SanadAgent system.
[!IMPORTANT]
🧭 Documentation is the most important part of this project
Treat every
AGENTS.mdfile as a Runtime Contract, not as optional notes. Poor documentation causes AI agent behavior drift, architecture drift, and incorrect changes in the wrong layers.
- Functional Discoverability: For a complete, curated index of all codebase features, components, and guides, read docs/llms.txt immediately.
- Operational Rules: Plan, coordinate, and execute tasks using Git Worktrees, dynamic port offsets, and multi-agent systems.
1. Documentation Hierarchy
This repository uses a nested web of contracts. The closer the document is to the code, the more technical it should be:
AGENTS.md(this file / repository root) — Main Master Contract governing all open-source components.- client/AGENTS.md — Owns Flutter client UI contracts, widgets, and state registries (Flutter).
- agent/AGENTS.md — Owns local Dart daemon interfaces, MCP servers, and background services (Dart).
Rules for AI Agents and Developers
- Always read the local
AGENTS.mdfile governing a subdirectory before making any edits in that directory. - Always update the relevant docs in the same session as the code change. This is a strict Definition of Done (DoD).
- Review the closest owning
AGENTS.mdfor every changed area. Update it only when the change alters a durable law, ownership boundary, invariant, or makes an existing statement stale; do not edit contracts merely to record implementation activity. - Keep higher-level docs abstract where appropriate and push implementation detail down into local leaf docs.
- Keep lower-level docs concrete, explicit, and practical.
- Remove stale or contradictory documentation immediately to prevent behavior drift.
- Use
README.mdonly as the public product source of truth for quick starts and pitches. Do not letREADME.mdbecome a competing implementation contract; durable architecture and development contracts belong here inAGENTS.mdand their nested child contracts. - Use
fvmfor all Flutter/Dart operations. Never execute global flutter/dart commands. - All referenced file paths must be relative to the workspace root.
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.
- 8d ago First seen · 194 lines · 3,115 tokens per session scan A a8fed27cfb32
sanad-agent AGENTS.md is an instructions file published in the GitHub repository EastStarAI/sanad-agent (42 stars, last pushed 2d ago), licensed MIT. It adds 3,115 tokens to every session, about $0.0156 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
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.