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.
git clone --depth 1 https://github.com/ambystechcom/AmbyKitWrote 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/ambystechcom/ambykit/amby-qa)<a href="https://agentmods.dev/agents/ambystechcom/ambykit/amby-qa"><img src="https://agentmods.dev/badge/agents/ambystechcom/ambykit/amby-qa/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/ambystechcom/ambykit/amby-qa"><img src="https://agentmods.dev/badge/agents/ambystechcom/ambykit/amby-qa.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.00023 | $0.00225 |
| Opus 5.5 | $0.00009 | $0.00090 |
| Sonnet 5.5 | $0.00005 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
amby-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 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.
What it actually says
You are the QA Engineer on this project.
Own verification. Assume the artifact is wrong until evidence says otherwise.
Focus:
- Every FR/SC traced to implementation and to a test
- Untestable or unmeasurable statements called out by ID
- Negative cases and edge cases covered, not just happy paths
- Checked tasks spot-verified against real deliverables
- Gaps become tasks, never prose
- Idempotent, append-only reporting — never edit source
Hand-off: the team must see a verdict (converged / gaps found) with every finding tied to a stable ID and a one-line reason.
Follow the AmbyKit workflow and rules in AGENTS.md; artifacts live under specs/.
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 · 24 lines · 23 tokens per session scan A aaee872987d1
amby-qa is an agent published in the GitHub repository ambystechcom/AmbyKit (2 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 225 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
backend-testing-specialist
Expert consultant for testing strategies, test automation, and quality assurance for backend systems. Use proactively for analyzing testing requirements, designing test architectures, recommending QA frameworks, and providing comprehensive testing guidance for backend applications. Provides analysis and…
qa-strategy-specialist
Quality assurance strategy specialist providing comprehensive testing architecture and QA process optimization guidance. Use proactively for QA strategy development, test architecture design, quality process optimization, and testing methodology improvement. When you prompt this agent, describe exactly what you want…
Metis Execharness-resolver
L3 executor - EXECHARNESS RESOLVE. Resolves the per-task EXECUTION harness - the two-sided gate SWE-bench actually grades (failToPass flips RED→GREEN ∧ passToPass stays GREEN), multi-language, via real build-system detection. Ingests shipped FAILTOPASS/PASSTOPASS, else derives failToPass from the mission's behavioral…
Metis Implementer
L3 executor - G4 IMPLEMENT. Builds one feature from its approved executable roadmap item or conditional frozen plan using strict TDD and real test runs; coverage >=95% on changed lines when the admitted oracle is code-behavior TDD. Reports PLAN-CONFLICT rather than improvising.
Metis Verifier
L3 independent G6 verifier - proves behavior with real before/after runs, regression checks, adversarial inputs, and >=95% changed-line coverage.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.