qa-orchestra: Instructions file for Claude Code

CLAUDE.md

qa-orchestra CLAUDE.md is an instructions file for Claude Code from Anasss/qa-orchestra. It costs 920 tokens per session, scanned A, original, MIT.

A set of Claude Code instructions for QA Orchestra, an open-source toolkit where specialized agents handle different software-testing tasks.

In plain words
What is it for?
Use it to set project context, check pull requests, start applications, review changes against requirements, and create test scenarios.
Why use it?
It gives the agents shared project information and a defined way to run QA work across different web technologies.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: reads .claude/ paths; mentions Claude Code.

This is Anasss/qa-orchestra's own configuration. It tells Claude Code how to work on qa-orchestra itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything qa-orchestra configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/Anasss/qa-orchestra/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/Anasss/qa-orchestra

Made for: Claude Code.

Wrote 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.

agentmods badge for qa-orchestra CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/anasss/qa-orchestra/claude-md.svg)](https://agentmods.dev/instructions/anasss/qa-orchestra/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/anasss/qa-orchestra/claude-md"><img src="https://agentmods.dev/badge/instructions/anasss/qa-orchestra/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 920 This file is loaded in full into every session.
When invoked 920 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00920 $0.00920
Opus 5 $0.00460 $0.00460
Sonnet 5 $0.00184 $0.00184
Haiku 4.5 $0.00092 $0.00092

Measured 6d ago against content hash 807f93581525, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

qa-orchestra CLAUDE.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 6d 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.

CLAUDE.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

QA Orchestra — Claude Code Instructions

@context/CONTEXT.md

What this project is

An open-source, multi-agent QA toolkit for Claude Code. Each QA task is handled by a specialized agent in .claude/agents/. Project context is auto-loaded from context/CONTEXT.md above.

Stack-agnostic. Works with any web application — React, Angular, Vue, Rails, Django, Spring Boot, or any other stack. All project-specific details live in context/CONTEXT.md.

Quick start

# 1. Clone into your workspace
git clone https://github.com/Anasss/qa-orchestra.git

# 2. Fill in your project context
cp examples/CONTEXT.example.md context/CONTEXT.md
# Edit context/CONTEXT.md with your stack details

# 3. Open Claude Code — agents auto-load from .claude/agents/
# Type @agent-name or describe what you need

How to invoke agents

# Full pipeline — checkout PR, run app, validate in browser, review diff, generate tests
"Run @orchestrator for PR #42 on my-backend and PR #38 on my-frontend"

# Direct invocation
"@environment-manager checkout feature/ISSUE-1 and start the app"
"@functional-reviewer compare this diff against these ACs: ..."
"@test-scenario-designer generate scenarios for these ACs: ..."
"@automation-writer read qa-output/test-scenarios.md and generate Playwright tests"
"@manual-validator guide me through qa-output/test-scenarios.md"
"@bug-reporter read qa-output/functional-review.md and create bug reports"
"@browser-validator validate scenarios against the running app"
"@release-analyzer analyze the diff between v1.0 and HEAD across all repos"
"@smart-test-selector which existing tests are affected by this diff?"

Agent map

Agent Model Reads Writes
orchestrator Sonnet ticket + inputs qa-output/plan.md
environment-manager Sonnet PR/branch + CONTEXT.md qa-output/environment-status.md
functional-reviewer Opus AC + diff + browser findings qa-output/functional-review.md
bug-reporter Sonnet functional-review + browser-validation qa-output/bug-reports.md
test-scenario-designer Sonnet AC qa-output/test-scenarios.md
automation-writer Sonnet test-scenarios.md qa-output/automation/
manual-validator Sonnet test-scenarios.md qa-output/validation-report.md
browser-validator Sonnet test-scenarios.md + Chrome MCP qa-output/browser-validation.md
release-analyzer Opus multi-repo diffs + AC qa-output/release-analysis.md
smart-test-selector Sonnet diff + existing tests qa-output/test-selection.md

Read the full file on GitHub · 93 lines

Changes

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.

  1. 6d ago First seen · 93 lines · 920 tokens per session scan A 807f93581525

Subscribe to this mod's changes

qa-orchestra CLAUDE.md is an instructions file published in the GitHub repository Anasss/qa-orchestra (12 stars, last pushed 4mo ago), licensed MIT. It adds 920 tokens to every session, about $0.0046 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.

Related

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).

microsoft/vscode · 6,785 tokens

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens