Borrowing it
Nothing to install: this file belongs to c9r-io/orchestrator. 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/c9r-io/orchestrator/main/.claude/skills/qa-testing/SKILL.mdgit clone --depth 1 https://github.com/c9r-io/orchestratorWrote 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/skills/c9r-io/orchestrator/qa-testing)<a href="https://agentmods.dev/skills/c9r-io/orchestrator/qa-testing"><img src="https://agentmods.dev/badge/skills/c9r-io/orchestrator/qa-testing/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/skills/c9r-io/orchestrator/qa-testing"><img src="https://agentmods.dev/badge/skills/c9r-io/orchestrator/qa-testing.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.00023 | $0.03411 |
| Opus 5.5 | $0.00009 | $0.01364 |
| Sonnet 5.5 | $0.00005 | $0.00682 |
| Haiku 4.5 | $0.00002 | $0.00341 |
Grade A, and why
qa-testing 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 2mo 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 — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Testing Skill
Execute scenario-based QA testing driven by docs/qa/**/*.md documents.
Prerequisites
CRITICAL: Always rebuild CLI before testing to ensure you have the latest version.
-
Rebuild CLI (REQUIRED - ensures latest code):
cargo build --release -p orchestrator-cli -p orchestratord -
Initialize orchestrator if needed — only when the database does not exist yet:
# `orchestrator init` is only for a genuinely absent runtime database. # The default runtime root is ~/.orchestratord; ORCHESTRATORD_DATA_DIR overrides it. orchestrator daemon status -
For QA scenario isolation — use project-scoped reset instead of destroying shared state:
# Delete a project's state (task data + config + auto-tickets) orchestrator delete project/<project> --force # Deploy fixtures into project scope (other projects untouched) orchestrator apply -f fixtures/manifests/bundles/<fixture>.yaml --project <project> -
QA docs exist under
docs/qa/. -
Optional: UI automation via browser tools.
Conventions / Configuration
API helper script: .claude/skills/tools/qa-api-test.sh
Environment variables:
API_BASE_URL(default:http://localhost:8080)API_TOKEN(optional)API_TOKEN_CMD(optional command that prints a token to stdout)
Notes:
- If the API does not require auth, omit
API_TOKENandAPI_TOKEN_CMD. - If the API requires auth, prefer providing a project-specific
API_TOKEN_CMD(for example, a script underscripts/).
Test Scripts Directory (scripts/qa/)
IMPORTANT: A collection of reusable QA test scripts may exist in scripts/qa/. Before writing any new test script, always check scripts/qa/ first for an existing script that covers the same or similar scenario.
- Reuse first: Run
ls scripts/qa/orGlob: scripts/qa/*to find existing scripts. If a matching script exists, use it directly (or adapt it) instead of creating a new one. - Create in
scripts/qa/: When a new test script is needed, always place it underscripts/qa/— never in the project root or other ad-hoc locations. - Naming convention: Follow existing patterns — e.g.,
test-{feature}.{js,mjs,py,sh}or{feature}_test.py.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 353 lines · 23 tokens per session scan A 0fd90f7d9094
qa-testing is a skill published in the GitHub repository c9r-io/orchestrator (21 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 3,411 once invoked, about $0.0001 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 skills, from other repositories
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
cw-dogfood
Use when a Codewhale change needs proving in the real product, or when asked to build/install/dogfood the local binaries: stamped release build, atomic install, fresh-shell verification, and the manual QA that gates cannot cover.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a…
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.