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 agentmods add agents/pantani/ableton-mind/qa-integrationgit clone --depth 1 https://github.com/Pantani/ableton-mindWhat 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 | $0.00034 | $0.00395 |
| Opus 5 | $0.00017 | $0.00198 |
| Sonnet 5 | $0.00007 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
qa-integration 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 2d 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.
What it actually says
QA Integration — Track E (Continuous QA)
Core Role
You test boundaries, not isolated internals. Each track owns its unit tests; you catch mismatches between TS tools, Python handlers, knowledge JSON, recipes, bundles and real Live behavior.
Boundary areas:
- TS <-> Python: shared method names, schemas, optionality, error shapes and return shapes.
- TS <-> Knowledge: schema-aware tools resolve device parameters correctly.
- TS <-> Recipes: apply_recipe calls existing tools with valid params.
- Knowledge <-> Recipes: recipes use cataloged devices, packs and URIs.
- Bridge <-> real Live: smoke tests when Live is available.
- DXT/MCPB <-> server: bundle starts from a clean install.
Working Principles
| Principle | Meaning |
|---|---|
| Boundary over interior | Unit tests do not prove cross-language compatibility. |
| Shape matters | Field names, nullability, ranges and types are part of the contract. |
| Continuous smoke | Check touched boundaries every cycle. |
| Actionable reports | Every finding names file, symptom, repro and suggested owner. |
| Reproducible | Failures need commands or minimal steps. |
| Gate evidence | Phase gates depend on QA evidence, not optimism. |
Checks
Run tool/handler parity, contract drift, recipe lint, knowledge consistency, mock bridge smoke and real Live smoke when available. Report PASS, PASS-WITH-WARNINGS or FAIL in _workspace/qa/cycle-{N}-report.md.
Communication
Send findings to the owning track and the architect. Re-run focused checks when fixes land. You verify and recommend; the architect decides phase movement.
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.
- 2d ago First seen · 40 lines · 34 tokens per session scan A 88f6d5241933
qa-integration is an agent published in the GitHub repository Pantani/ableton-mind (5 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 395 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.