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 anhtester/antigravity-testing-kit --skill qa_automation_engineergit clone --depth 1 https://github.com/anhtester/antigravity-testing-kitWrote 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/anhtester/antigravity-testing-kit/qa_automation_engineer)<a href="https://agentmods.dev/skills/anhtester/antigravity-testing-kit/qa_automation_engineer"><img src="https://agentmods.dev/badge/skills/anhtester/antigravity-testing-kit/qa_automation_engineer/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/anhtester/antigravity-testing-kit/qa_automation_engineer"><img src="https://agentmods.dev/badge/skills/anhtester/antigravity-testing-kit/qa_automation_engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00041 | $0.02102 |
| Opus 5.5 | $0.00016 | $0.00841 |
| Sonnet 5.5 | $0.00008 | $0.00420 |
| Haiku 4.5 | $0.00004 | $0.00210 |
Grade A, and why
QA Automation Engineer 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- QA Automation Engineer — 92% identical, 7 lines differ
How it starts
The opening of the file, as written. The whole thing — 369 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Automation Engineer
Description
This skill enables the agent to assist with software testing and automation tasks.
The agent can:
- Generate manual test cases from requirements
- Generate test automation scripts from test cases or UI flows
- Generate API tests from Swagger/OpenAPI specifications
- Explore applications and discover test scenarios
- Generate automation frameworks
- Generate test data
- Analyze flaky tests
- Generate stable locators
- Generate requirements from website analysis
This skill is designed for modern QA workflows and automation development.
When to Use
Use this skill when the user asks about:
- Test automation
- Manual testing
- Automation frameworks
- API testing
- UI testing
- Test data generation
- Flaky test debugging
- Locator generation
- Requirements analysis from website
- Jira integration (fetch requirements, push test results)
- Xray test management
Typical prompts include:
- Generate test cases from requirement
- Generate Selenium automation from test case
- Generate automation from UI steps
- Generate API tests from Swagger
- Generate regression suite → (redirect sang
generate_application_test_planhoặcgenerate_manual_testcases_rbt) - Generate test data
- Analyze flaky test
- Generate locator for element
- Generate requirements from website
Workflow Routing
When the user request matches a specific task, select the appropriate workflow file from .agent/workflows/.
Generate test cases from requirements
Delegate: Tác vụ này thuộc skill
rbt_manual_testing— không phảiqa_automation_engineer.
Use workflow: generate_testcases_from_requirements (QUICK mode) hoặc generate_manual_testcases_rbt (FULL RBT mode).
Triggers when user asks:
- generate test cases → delegate to
rbt_manual_testing(QUICK mode) - write manual test cases → delegate to
rbt_manual_testing(QUICK mode) - test scenarios from requirement → delegate to
rbt_manual_testing(QUICK mode) - sinh test cases đầy đủ / quy trình 6 bước → delegate to
rbt_manual_testing(FULL RBT mode)
What ships with it
3 files 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.
- 1mo ago First seen · 369 lines · 41 tokens per session scan A d3847df4d158
QA Automation Engineer is a skill published in the GitHub repository anhtester/antigravity-testing-kit (147 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 2,102 once invoked, about $0.0002 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-30.
Other skills, from other repositories
shaft-developer
Use when starting any SHAFT testing task to select exactly one lifecycle, implementation, or tool specialist before doing the work.
shaft-test-case-design
Use when designing reviewable test cases or scenarios with traceability, data, steps, expected results, techniques, priorities, and boundary coverage.
shaft-accessibility-testing
Use when testing web or mobile accessibility for WCAG conformance, keyboard and focus behavior, semantics, errors, or user impact.
shaft-api-testing
Use when implementing or repairing SHAFT.API tests for HTTP requests, authentication, payloads, schemas, responses, contracts, or service workflows.
shaft-automated-test-authoring
Use when implementing or repairing executable SHAFT Java tests for web, mobile, API, database, CLI, TestNG, JUnit, or Cucumber behavior.
shaft-change-verification
Use when edited SHAFT Java needs a reuse plan, preview diff, guardrail check, approved application, focused test, and evidence-backed verdict.