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 GuitarAlchemist/ga --skill qa-collaborationgit clone --depth 1 https://github.com/GuitarAlchemist/gaWrote 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/guitaralchemist/ga/qa-collaboration)<a href="https://agentmods.dev/skills/guitaralchemist/ga/qa-collaboration"><img src="https://agentmods.dev/badge/skills/guitaralchemist/ga/qa-collaboration.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.00044 | $0.01592 |
| Opus 5 | $0.00022 | $0.00796 |
| Sonnet 5 | $0.00009 | $0.00318 |
| Haiku 4.5 | $0.00004 | $0.00159 |
Grade A, and why
QA Collaboration 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 7d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Collaboration
This is the rubric for collaborating with Guitar Alchemist's senior QA agent. Read it before opening a PR, proposing a refactor, or shipping a metric-moving change. It is a checklist, not a narrative — follow it in order.
1. Who the QA Engineer Is
Two surfaces of the same role:
QAArchitectAgent—Common/GA.Business.ML/Agents/QAArchitectAgent.cs. Synchronous, in-process, callable from any C# code. Returns aQaVerdict.qa-architect-cycle.ixql—Demerzel/pipelines/qa-architect-cycle.ixql. Long-running, governance-grade, runs on PR open/sync and on a daily 06:00 UTC sweep. Persists verdicts tostate/quality/verdicts/.
They both speak the same protocol: the QaVerdict contract.
2. The Contract Is Not Optional
- Source of truth:
docs/contracts/2026-05-02-qa-verdict.contract.md. - JSON Schema:
docs/contracts/qa-verdict.schema.json. - Schema is draft v0.1.0, will freeze at v1.0.0 after a 2-sprint soak. Adding a new evidence kind, risk tier, or producer slug requires amending the contract markdown AND bumping the schema, not silently extending the JSON.
3. The 8 MCP Primitives
Available from the GaQaMcp MCP server. Treat them as your hands — call them rather than re-implementing.
| Tool | Call when… | Returns |
|---|---|---|
qa_assess_blast_radius |
Before designing a non-trivial change | blast_radius object: layers touched, one-way doors crossed, invariants at risk, score 0..1 |
qa_gap_analyze |
After writing code, before opening a PR | Array of followup candidates surfacing untested critical paths |
qa_propose_tests |
When adding new components or breaking out abstractions | Array of test stubs (path + body) grounded in repo patterns |
qa_verify_invariants |
Before merging changes that touch Core / Domain / Analysis / AI/ML | evidence{kind: contract_check} items, one per invariant |
qa_replay_adversarial |
Before merging changes to chord/voicing/embedding pipelines | evidence{kind: adversarial_replay} |
qa_score_quality_drift |
When changes may move a metric in state/quality/*.json |
evidence{kind: quality_snapshot} with delta + guardrail check |
qa_lookup_defect_memory |
Before designing — surfaces "we got burned by this before" | Array of past followups matching the touched components |
qa_emit_verdict |
At the end, to persist a verdict | Path of the persisted JSON + verdict_id |
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.
- 7d ago First seen · 89 lines · 44 tokens per session scan A 3b3cf7d07d91
QA Collaboration is a skill published in the GitHub repository GuitarAlchemist/ga (2 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 1,592 once invoked, about $0.0002 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.