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 griddynamics/rosetta --skill qa-knowledgegit clone --depth 1 https://github.com/griddynamics/rosettaWrote 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/griddynamics/rosetta/qa-knowledge)<a href="https://agentmods.dev/skills/griddynamics/rosetta/qa-knowledge"><img src="https://agentmods.dev/badge/skills/griddynamics/rosetta/qa-knowledge/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/griddynamics/rosetta/qa-knowledge"><img src="https://agentmods.dev/badge/skills/griddynamics/rosetta/qa-knowledge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.02095 |
| Opus 5.5 | $0.00013 | $0.00838 |
| Sonnet 5.5 | $0.00006 | $0.00419 |
| Haiku 4.5 | $0.00003 | $0.00210 |
Grade A, and why
qa-knowledge 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<qa_knowledge>
QA-engineering skill. Runs the QA flow -- code analysis, requirements synthesis, gap analysis, scenario/spec design, QA test implementation, failure triage -- over the QA knowledge base (failure taxonomies, catalogs, artifact skeletons) it owns. Emits into the provided artifact contract; never invents its shape or path.
<when_to_use_skill>
Use for QA-engineering work on backend-API or UI/E2E tests: synthesizing collected sources into requirements, analyzing gaps/contradictions, designing test scenarios / specs / TMS cases, implementing QA tests (UI / API / selectors) from a plan or approved specs, triaging execution failures, or recovering test-automation architecture / API contracts. Also supplies the QA conventions and artifact skeletons these tasks emit. Plain unit/integration test writing is skill testing, not this flow. TestRail/Jira/Confluence are canonical examples, adapt to the current case.
</when_to_use_skill>
- MUST USE SKILL
reverse-engineeringfor thecode_analysismode (test-automation architecture analysis, API-contract extraction). - USE SKILL
codingfor repo conventions;debuggingfor failing tests;sensitive-datafor redaction (canonical authority). - USE SKILL
qa-structurefor QA paths / identifiers / state at point of use.
<core_concepts>
- Load only what the current task needs; artifact skeletons are assets, conventions/catalogs are references -- READ SKILL FILE at point of use (see
<resources>). - Per-value honesty: every concrete value traces to a loaded source, a user clarification, or an explicit
[ASSUMED: ...]/gap: ...marker -- no confident fabrication. - Coverage is total: every input requirement / case / failure maps to ≥1 emitted item OR an explicit excluded/gap entry -- no silent drops.
- Redaction: scan every emitted artifact and redact credentials/tokens/PII/credentialed-URLs before writing → USE SKILL
sensitive-data. - Invocation: an owning phase supplies bindings (paths, IDs, workflow-state path) and deferred decisions. Standalone (no phase) -- ask the user for each and surface outputs to them; never write an assumed workflow-state path. "Ask the phase" in a reference = ask the user; never stall on a decision that cannot arrive.
</core_concepts>
<mode_selection>
Pick exactly one mode by deliverable (multi-phase → run the earliest, stop; the next phase re-invokes); read its reference via <resources>. No clean match → name the closest mode and confirm, never silently pick. (Plain unit/integration tests are skill testing, not a mode here.)
- code → test-arch map / API contract → code_analysis (analysis, no tests; via prereq skill
reverse-engineering) - collected sources → one requirements doc → synthesis (redact before quoting)
- find gaps/contradictions, no fixing → gap_analysis (analysis-only: surface each finding and STOP)
- design test cases/specs incl. TMS, not runnable → scenario_design
- write runnable QA tests (UI / API / selectors) from a plan/specs → implementation_modes
- categorize run-report failures, no fixing → test_execution_triage (read-only)
- propose fixes for failing QA tests + gain explicit approval to apply → correction (HITL-gated: present → approve → apply; via
coding/debugging)
</mode_selection>
Router -- READ SKILL FILE for the one your current step needs (point-of-use, never all at once):
| When you need to… | Command |
|---|---|
present a correction for approval (API-AQA or UI-AQA) (<correction> mode) |
READ SKILL FILE assets/proposed-change-template.md |
run the explicit-approval gate for a correction or spec/plan approval (<correction> mode) |
READ SKILL FILE assets/approval-gate.md |
| emit the QA api-analysis artifact | READ SKILL FILE assets/api-analysis-template.md |
emit QA test specs (Given-When-Then ATC-NNN) |
READ SKILL FILE assets/test-spec-template.md |
| record the API-AQA test-implementation | READ SKILL FILE assets/api-aqa-test-impl-record.md |
| emit the API-AQA execution report | READ SKILL FILE assets/failure-report-template.md |
| record QA gap-analysis findings (G/C/A) | READ SKILL FILE assets/gap-finding-templates.md |
| build the UI-AQA test plan | READ SKILL FILE assets/ui-aqa-plan-template.md |
| emit the UI-AQA code-analysis report | READ SKILL FILE assets/code-analysis-report-template.md |
| run UI-AQA clarification (gap entry / questions / typed assertions) | READ SKILL FILE assets/ui-aqa-clarification-templates.md |
| record the UI-AQA test-implementation | READ SKILL FILE assets/ui-aqa-test-impl-record.md |
| emit the UI-AQA failure analysis | READ SKILL FILE assets/failure-report-template.md |
| send the page-source capture message to the user | READ SKILL FILE assets/page-source-capture-instructions.md |
| classify an API-AQA backend-API failure | READ SKILL FILE references/api-aqa-failure-taxonomy.md |
| classify an UI-AQA UI/E2E failure | READ SKILL FILE references/ui-aqa-failure-taxonomy.md |
synthesize collected sources into a requirements document (<synthesis> mode) |
READ SKILL FILE references/synthesis-catalogs.md |
run QA gap-analysis detection (<gap_analysis> mode) |
READ SKILL FILE references/gap-analysis-catalogs.md |
design Given-When-Then API specs -- taxonomy + ATC template (<scenario_design> mode) |
READ SKILL FILE references/gwt-spec.md |
| format test cases for the configured TMS (scenario_design vendor binding) | READ SKILL FILE references/<vendor>-format.md (<vendor> from project config; TestRail shipped → testrail-format.md) |
| export a case set to the configured TMS (vendor binding + destructive-write gate) | READ SKILL FILE references/<vendor>-export.md (<vendor> from project config; TestRail shipped → testrail-export.md) |
| fork a TMS format/export binding to another vendor | READ SKILL FILE references/vendor-fork-guide.md |
implement UI / API / selector tests -- code + selector tables + templates (<implementation_modes> mode) |
READ SKILL FILE references/implementation-examples.md |
analyze test-automation architecture or extract API contracts (<code_analysis> mode, via reverse-engineering) |
READ SKILL FILE references/analysis-modes.md |
triage automated-test execution failures (<test_execution_triage> mode) |
READ SKILL FILE references/test-execution-triage.md |
What ships with it
24 files 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.
- assets/api-analysis-template.md 4.3 KB
- assets/api-aqa-test-impl-record.md 1.5 KB
- assets/approval-gate.md 1.6 KB
- assets/code-analysis-report-template.md 2.8 KB
- assets/failure-report-template.md 3.0 KB
- assets/gap-finding-templates.md 2.9 KB
- assets/page-source-capture-instructions.md 3.1 KB
- assets/proposed-change-template.md 3.0 KB
- assets/test-spec-template.md 1.9 KB
- assets/ui-aqa-clarification-templates.md 5.0 KB
- assets/ui-aqa-plan-template.md 2.7 KB
- assets/ui-aqa-test-impl-record.md 2.4 KB
- README.md 2.8 KB
- references/analysis-modes.md 3.2 KB
- references/api-aqa-failure-taxonomy.md 991 B
- references/gap-analysis-catalogs.md 6.0 KB
- references/gwt-spec.md 8.5 KB
- references/implementation-examples.md 9.3 KB
- references/synthesis-catalogs.md 7.1 KB
- references/test-execution-triage.md 1.8 KB
- references/testrail-export.md 7.8 KB
- references/testrail-format.md 8.4 KB
- references/ui-aqa-failure-taxonomy.md 1.0 KB
- references/vendor-fork-guide.md 2.9 KB
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 · 115 lines · 32 tokens per session scan A 46c020b10ea1
qa-knowledge is a skill published in the GitHub repository griddynamics/rosetta (360 stars, last pushed today), licensed Apache-2.0. It adds 32 tokens to every session and 2,095 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-09-03.
Other skills, from other repositories
webapp-qa
Perform scoped exploratory QA of a web application, reproduce defects, collect screenshots and console evidence, and deliver a prioritized report.
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
debugging
Playwright test debugging conventions for the scaffold — reading failure messages, classifying failure modes (TimeoutError, ZodError, strict-mode violation, locator not found, network errors, schema drift), the playwright.config.ts capture defaults (trace on-first-retry, screenshot only-on-failure, video…
Flaky Test Doctor
Diagnose flaky test failures from Playwright reports, traces, and rerun history. Classify each failure as product, test, environment, data, or unknown with cited evidence and a proposed fix. Never auto-modifies code without opt-in.
flutter-skill
Automate and test Flutter applications — launch apps, inspect widgets, tap elements, enter text, scroll, swipe, take screenshots, validate state, and debug via Dart VM Service Protocol. Use when the user wants to run Flutter app tests, automate Flutter UI interactions, inspect widget trees, debug a running Flutter…
lov-runtime-verification
Verify client runtime fixes on actual desktop builds, physical iOS/Android devices, React Native/Flutter hosts, and deployed Web/PWA browsers with comparable workloads and lifecycle checks.