Borrowing it
Nothing to install: this file belongs to wonna-fi/saaga. 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/wonna-fi/saaga/main/AGENTS.mdgit clone --depth 1 https://github.com/wonna-fi/saagaWrote 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/wonna-fi/saaga/agents-md)<a href="https://agentmods.dev/instructions/wonna-fi/saaga/agents-md"><img src="https://agentmods.dev/badge/instructions/wonna-fi/saaga/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/wonna-fi/saaga/agents-md"><img src="https://agentmods.dev/badge/instructions/wonna-fi/saaga/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.00417 | $0.00417 |
| Opus 5.5 | $0.00167 | $0.00167 |
| Sonnet 5.5 | $0.00083 | $0.00083 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
saaga 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 1mo 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.
What it actually says
Development Rules
Definition of Done Checklist
A task is ready when the following criteria are met:
- The implementation fulfills the requirements
- The implementation has tests
- The complete test suite passes
- There are no linter errors
Domain Documentation (saaga)
This codebase has structured domain documentation under saaga-docs/, organized into four types:
| Type | Index | Answers |
|---|---|---|
| Concepts | saaga-docs/concepts/INDEX.md |
What something is and where it lives |
| Patterns | saaga-docs/patterns/INDEX.md |
How to do common operations — anything that takes reading a code flow to follow |
| Conventions | saaga-docs/conventions/INDEX.md |
What things must be named or shaped like — the rules you could check with grep |
| Features | saaga-docs/features/INDEX.md |
How a feature works end-to-end, user-facing or internal machinery |
Classify your question, open the matching INDEX.md, and read the relevant document(s):
- "What is X / where does X live?" -> read a concept
- "How do I do X?" -> read a pattern
- "What do I call X / where does the file go?" -> read a convention
- "How does feature X work end-to-end?" -> read a feature
Not every codebase has conventions; the category is present only when there are rules worth stating.
Rules:
- Docs first: ALWAYS read the domain documentation BEFORE exploring source code. It is the authoritative source for understanding the system; source code is the second resort.
- No documentation updates during implementation: do NOT update the domain documentation when making code changes. It is maintained separately by Saaga.
- Consult before implementing: before implementing new features or changes, check the existing concepts and patterns to reuse existing services/modules instead of reinventing them.
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.
- 1mo ago Changed · -1 lines · -114 tokens per session 7a16f61fcd41
- 2mo ago First seen · 40 lines · 531 tokens per session scan A 9da130ca49aa
saaga AGENTS.md is an instructions file published in the GitHub repository wonna-fi/saaga (7 stars, last pushed 4d ago), licensed MIT. It adds 417 tokens to every session, about $0.0017 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-31.
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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.