Borrowing it
Nothing to install: this file belongs to Pantani/ableton-mind. 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/Pantani/ableton-mind/main/.claude/agents/qa-integration.mdgit clone --depth 1 https://github.com/Pantani/ableton-mindWrote 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/agents/pantani/ableton-mind/qa-integration)<a href="https://agentmods.dev/agents/pantani/ableton-mind/qa-integration"><img src="https://agentmods.dev/badge/agents/pantani/ableton-mind/qa-integration/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/agents/pantani/ableton-mind/qa-integration"><img src="https://agentmods.dev/badge/agents/pantani/ableton-mind/qa-integration.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.00034 | $0.00395 |
| Opus 5.5 | $0.00014 | $0.00158 |
| Sonnet 5.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 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.
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.
- 2mo 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 (10 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 395 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-31.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
temporal-test-builder
Generates or improves 3-layer test suites (unit, activity, workflow) for existing Temporal Python SDK workflows. Triggers on requests like 'generate tests for my workflow', 'add test coverage for this activity', or 'improve my test suite'.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…