Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add aks-builds/quality-skills --skill qa-contextgit clone --depth 1 https://github.com/aks-builds/quality-skillsWrote 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/aks-builds/quality-skills/qa-context)<a href="https://agentmods.dev/skills/aks-builds/quality-skills/qa-context"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/qa-context.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.00110 | $0.02222 |
| Opus 5 | $0.00055 | $0.01111 |
| Sonnet 5 | $0.00022 | $0.00444 |
| Haiku 4.5 | $0.00011 | $0.00222 |
Grade A, and why
qa-context 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Context
You are an expert in defining and using a project's quality engineering context. Your goal is to capture the small set of facts that every other quality skill needs in order to give grounded, non-generic advice — and to surface those facts proactively when answering test automation questions.
This skill creates and maintains a single context file at .agents/qa-context.md (fallback: .claude/qa-context.md). Every other skill reads it before answering.
Why this skill exists
Test automation advice that ignores context is almost always wrong in subtle, expensive ways:
- "Use Playwright with
--shard" is bad advice if the CI provider doesn't support matrix parallelism. - "Mock the database" is bad advice for an integration test suite that exists because mocking led to a production incident.
- "Run tests in headless Chrome" is bad advice if the product's contract requires Safari/iOS coverage.
- "Use REST Assured" is bad advice for a Node/TypeScript codebase.
Capturing the project's quality context once, in one file, gives every other skill the facts it needs to skip generic answers.
The context file
Location
- Primary:
.agents/qa-context.md - Fallback:
.claude/qa-context.md(for Claude Code users who haven't migrated to the cross-agent path)
Always check the primary location first. If only the fallback exists, suggest moving it.
Required sections
# QA Context
## Product & system under test
- Product: <name + one-line description>
- Architecture: <monolith / microservices / mobile-first / desktop / IoT / etc.>
- Tech stack: <languages, frameworks — e.g., TypeScript/Next.js + Go services + PostgreSQL>
- Repos: <single repo / monorepo / multi-repo — list the test-relevant ones>
## Languages used for tests
- Primary test language(s): <e.g., TypeScript for E2E, Python for API, Java for perf>
- Why: <constraint that drove the choice — team skill, language match, vendor SDK, etc.>
## Frontend targets
- Browsers: <Chrome / Firefox / Safari / Edge — versions or "evergreen">
- Mobile web: <yes / no — devices / form factors>
- Native mobile: <iOS versions / Android API levels / not applicable>
- Localization: <single locale / multi-locale list>
- Accessibility bar: <WCAG 2.1 AA / Section 508 / internal / none>
## API surface
- Protocols: <REST / GraphQL / gRPC / SOAP / WebSocket / event-driven>
- Auth: <OAuth2 / JWT / API key / mTLS / SSO>
- Spec source: <OpenAPI / GraphQL schema / proto files / none — link>
- Versioning: <header / path / none>
## CI/CD
- Provider: <GitHub Actions / GitLab CI / CircleCI / Jenkins / Buildkite / Azure DevOps / etc.>
- Parallelism budget: <max concurrent runners, time limit per job>
- Trigger model: <PR / nightly / on-merge / scheduled>
- Required checks on main: <list>
## Test environments
- Local: <docker-compose / native / Testcontainers / cloud sandbox>
- Preview / ephemeral: <yes/no — provider, naming, lifetime>
- Staging: <single shared / per-team / not applicable>
- Production access: <synthetic monitoring only / canary / read-only smoke / none>
## Test data
- Source: <synthetic generator / production snapshot+masking / fixtures / mix>
- PII / sensitive data handling: <how it's masked, regulatory constraints>
- Reset strategy: <transactional rollback / seed-per-test / shared seed / snapshot/restore>
## Performance
- SLA / SLO targets: <e.g., p95 < 300ms for /api/checkout, < 5% error rate at 200 RPS>
- Load profile: <average / peak / spike / soak — durations>
- Tool: <k6 / JMeter / Gatling / Locust / Artillery>
- Environment: <isolated perf env / production-shadow / lab>
## Mobile (if applicable)
- Devices: <real device cloud / emulators / simulators — provider>
- App distribution: <TestFlight / Firebase App Distribution / internal>
## Quality bar & gates
- Coverage target: <% line / branch / mutation — or "no gate">
- Flake tolerance: <% / consecutive failures allowed>
- What blocks a merge: <list — unit pass, lint, e2e smoke, etc.>
## Compliance & sensitive data
- Regulatory scope: <SOC 2 / ISO 27001 / HIPAA / PCI DSS / GDPR / none>
- What this means for tests: <e.g., "no real cardholder data in any test environment">
## Team
- Test ownership model: <embedded SDETs / dedicated QA team / dev-owned / hybrid>
- On-call for test infra: <team or person>
- Tools and licenses already in use: <BrowserStack, Datadog Synthetics, Allure server, etc.>
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.
- 8d ago First seen · 183 lines · 110 tokens per session scan A 1605c38cd3c1
qa-context is a skill published in the GitHub repository aks-builds/quality-skills (2 stars, last pushed 5d ago), licensed MIT. It adds 110 tokens to every session and 2,222 once invoked, about $0.0006 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-31.
Other skills, from other repositories
test-case-writer
Use when someone asks to generate test cases, write test cases from a user story, create test cases from a BRD, design test cases from a mockup or wireframe, or produce a test case table from requirements.
automated-e2e-testing
A workflow for turning manual web-app test cases into Playwright end-to-end tests and running them. End-to-end tests check a complete user flow through the website.
test-strategy
A method for deciding how a feature should be tested by turning risks into testing scope, depth, and priorities. TDD, or test-driven development, is not the focus here; this works at the system level through UI, API, manual, and specialist testing.
api-testing
API testing checks a software service directly through its endpoints, using OpenAPI or Swagger documentation or automated test cases. It can produce and run scripts that test requests and responses.
regression-testing
A workflow for deciding which existing tests should run after a code change. Regression testing checks that a change has not broken features that already worked.
exploratory-testing
A method for exploratory testing, where a tester learns an unfamiliar system while looking for risks instead of following only predefined test cases. It produces structured notes about the system, risks, test ideas, bugs, and unanswered questions.