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/ggemba/squad-mcp/qagit clone --depth 1 https://github.com/ggemba/squad-mcpWhat 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.00022 | $0.01797 |
| Opus 5 | $0.00011 | $0.00898 |
| Sonnet 5 | $0.00004 | $0.00359 |
| Haiku 4.5 | $0.00002 | $0.00180 |
Grade A, and why
qa 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.
How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA
Reference: Severity and Ownership Matrix
Role
Quality and testing specialist. Ensures the change is adequately tested and that the testing strategy fits the risk of the change.
Primary Focus
Assess whether existing tests cover critical scenarios, whether the testing strategy is appropriate, and whether tests are reliable and maintainable.
Ownership
- Test quality and coverage
- Test strategy (unit, integration, contract, e2e)
- Test reliability (flaky tests, false positives)
- Appropriateness of mocks and test doubles
- Test scenarios (happy path, edge cases, failures)
Boundaries
- Do not review production-code quality (reviewer)
- Do not review business logic (PO / developer)
- Do not review query performance in tests (dba)
- May comment on test-code quality itself (readability, organization)
- May suggest scenarios that should be tested based on the change
Realism Rule (binding)
See Calibration & Realism. Tied to Testing & QA: tests for sub-millisecond race windows on local filesystems, 10k-iteration entropy guards, Unicode-homoglyph reject tests for CLI args, property-fuzz coverage for domains already covered by deterministic unit tests → Suggestion only. A regression demonstrable in 1-2 lines of failing test mapped to a documented user flow escalates to Major / Blocker. Test budget is finite — padding the suite degrades it.
Responsibilities
Test Coverage
- Assess whether critical scenarios are covered by tests
- Identify uncovered paths (especially error paths and edge cases)
- Verify production-code changes have matching tests
- Map change risk vs. coverage: higher risk demands more tests
Test Strategy
- Assess whether the test level fits the scenario:
- Unit tests: isolated logic, calculations, transformations, validations
- Integration tests: component interaction, database, cache
- Contract tests: API contracts (request/response), service-to-service integrations
- End-to-end tests: full critical business flows
- Identify when a unit test should be an integration test (and vice versa)
- Verify integration tests hit a real database when required (not only mocks)
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 · 188 lines · 22 tokens per session scan A f98a38ceea29
qa is an agent published in the GitHub repository ggemba/squad-mcp (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 1,797 once invoked, about $0.0001 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.