Borrowing it
Nothing to install: this file belongs to Anasss/qa-orchestra. 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/Anasss/qa-orchestra/main/AGENTS.mdgit clone --depth 1 https://github.com/Anasss/qa-orchestraWrote 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/anasss/qa-orchestra/agents-md)<a href="https://agentmods.dev/instructions/anasss/qa-orchestra/agents-md"><img src="https://agentmods.dev/badge/instructions/anasss/qa-orchestra/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/anasss/qa-orchestra/agents-md"><img src="https://agentmods.dev/badge/instructions/anasss/qa-orchestra/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.01377 | $0.01377 |
| Opus 5.5 | $0.00551 | $0.00551 |
| Sonnet 5.5 | $0.00275 | $0.00275 |
| Haiku 4.5 | $0.00138 | $0.00138 |
Grade A, and why
qa-orchestra 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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — QA Orchestra Behavioral Instructions
This file defines how AI agents must behave in this project.
Primary support: Claude Code. Best-effort: any agent runtime that honors AGENTS.md and reads Markdown instructions. Tool names in agent frontmatter (Agent, Bash, etc.) are Claude Code conventions; other runtimes may need a tool-mapping layer before the agents work correctly.
0. Mandatory skill check (read this first)
Before responding to any QA-adjacent request, state which qa-orchestra agent applies. If one does, invoke it. If none does, say so explicitly and only then proceed with inline reasoning. Do not silently do QA-style work (gap analysis, scenario design, test selection, bug writing) without first naming the agent that owns that work — this is how specialist agents get forgotten and the discipline drifts.
Quick map:
- "Does this diff implement the AC?" →
functional-reviewer - "What scenarios do I need?" →
test-scenario-designer - "Which tests will this change break?" →
smart-test-selector - "File this as a bug." →
bug-reporter - "Check the app in a browser." →
browser-validator - "Set up the PR branch locally." →
environment-manager - "Write Playwright/Cypress tests for these scenarios." →
automation-writer - "Walk me through manual test execution." →
manual-validator - "Analyze this release across repos." →
release-analyzer - "Coordinate the full QA pipeline." →
orchestrator
1. Before every task
- Project context is auto-loaded via
@context/CONTEXT.mdin CLAUDE.md — do not re-read it manually. - Check
context/annotations/— scan for any annotation file relevant to your current task. - Check
qa-output/— if a prior agent already ran, read its output file before starting. - Check
qa-output/environment-status.md— if the environment manager has run, use its status to understand which branches are checked out and which services are running.
2. Environment-first principle
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 First seen · 125 lines · 1,377 tokens per session scan A d9a92385e6f6
qa-orchestra AGENTS.md is an instructions file published in the GitHub repository Anasss/qa-orchestra (14 stars, last pushed 6mo ago), licensed MIT. It adds 1,377 tokens to every session, about $0.0055 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).
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.