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 iradoweck/antigravity-awesome-skills --skill agent-qa-authoringgit clone --depth 1 https://github.com/iradoweck/antigravity-awesome-skillsWrote 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/iradoweck/antigravity-awesome-skills/agent-qa-authoring)<a href="https://agentmods.dev/skills/iradoweck/antigravity-awesome-skills/agent-qa-authoring"><img src="https://agentmods.dev/badge/skills/iradoweck/antigravity-awesome-skills/agent-qa-authoring/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/skills/iradoweck/antigravity-awesome-skills/agent-qa-authoring"><img src="https://agentmods.dev/badge/skills/iradoweck/antigravity-awesome-skills/agent-qa-authoring.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.01078 |
| Opus 5 | $0.00017 | $0.00539 |
| Sonnet 5 | $0.00007 | $0.00216 |
| Haiku 4.5 | $0.00003 | $0.00108 |
Grade A, and why
agent-qa-authoring 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 8d 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.
This is a copy
94% identical to agent-qa-authoring — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent QA Authoring
Overview
Author Agent QA tests, suites, and hooks without inventing schema fields or identifiers. Prefer Agent QA's MCP tools, use the bundled contract reference for exact fields, and validate every definition before saving or running it.
When to Use
- Creating or editing an Agent QA test, suite, or hook.
- Validating Agent QA YAML or canonical IDs.
- Running a newly authored Agent QA definition through MCP or CLI.
- Investigating which Agent QA configuration fields or workspace patterns apply.
Preconditions and Approval Boundary
- Work only in a configured Agent QA workspace that the user has authorized.
- Inspect the requested scope before any create, update, delete, or test-run operation.
- Obtain explicit confirmation before deleting a definition or running a test that can change external application state.
- Keep credentials out of definitions and output; use the workspace's configured secret handling.
Workflow
- Discover the local surface with
agent_qa_discover. - Inspect active config with
agent_qa_get_config, especially targets, devices, providers, andservices.mcp. - Load
references/agent-qa-contracts.jsonwhen exact schema fields or ID contracts are needed. - Generate every new ID with Agent QA tooling:
- MCP:
agent_qa_generate_id - CLI fallback:
agent-qa ids generate <test|suite|hook|run|observation> - If neither surface is already installed, stop and ask the user to approve
an exact Agent QA installation. Do not fetch and execute the package at
runtime through
npxor another moving package reference.
- MCP:
- Never hand-write IDs. Validate existing IDs with
agent_qa_validate_idoragent-qa ids validate <type> <id> --json. - Validate definitions before saving:
- Tests:
agent_qa_validate_testoragent_qa_validate_definitionwithkind: "test" - Suites:
agent_qa_validate_suiteoragent_qa_validate_definitionwithkind: "suite" - Hooks:
agent_qa_validate_definitionwithkind: "hooks"
- Tests:
- Prefer MCP authoring mutations:
- Tests:
agent_qa_create_test,agent_qa_update_test,agent_qa_delete_test - Suites:
agent_qa_create_suite,agent_qa_update_suite,agent_qa_delete_suite - Hooks:
agent_qa_create_hook,agent_qa_update_hook,agent_qa_delete_hook
- Tests:
- Use CLI or YAML fallback only when MCP is unavailable. Keep file paths matched by
workspace.testMatchorworkspace.suiteMatch.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 96 lines · 34 tokens per session scan A 018c5d1168cb
agent-qa-authoring is a skill published in the GitHub repository iradoweck/antigravity-awesome-skills (30 stars, last pushed 11d ago), licensed MIT. It adds 34 tokens to every session and 1,078 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to agent-qa-authoring, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
agent-qa-authoring
Create, edit, validate, and run Agent QA tests, suites, and hooks through MCP or CLI while preserving canonical IDs and schema contracts.
qa-acceptance
Produce QA acceptance criteria and a manual validation plan for a feature change — golden path, edge cases, error states, performance limits, and explicit pass/fail evidence.
agent-qa-debug-fix
Debug, patch, and verify failed Agent QA runs from MCP evidence, artifacts, logs, and local code without hiding product or infrastructure defects.
agent-qa-result-triage
Triage failed Agent QA runs with MCP evidence, artifacts, logs, fixed failure categories, confidence, and actionable next steps.
test-suite-architect
This skill should be used when establishing comprehensive QA testing processes for any software project. Use when creating test strategies, writing test cases following Google Testing Standards, executing test plans, tracking bugs with P0-P4 classification, calculating quality metrics, or generating progress reports.…
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.