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 fugazi/test-automation-skills-agents --skill grill-me-qagit clone --depth 1 https://github.com/fugazi/test-automation-skills-agentsWrote 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/fugazi/test-automation-skills-agents/grill-me-qa)<a href="https://agentmods.dev/skills/fugazi/test-automation-skills-agents/grill-me-qa"><img src="https://agentmods.dev/badge/skills/fugazi/test-automation-skills-agents/grill-me-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/skills/fugazi/test-automation-skills-agents/grill-me-qa"><img src="https://agentmods.dev/badge/skills/fugazi/test-automation-skills-agents/grill-me-qa.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.00081 | $0.03467 |
| Opus 5 | $0.00041 | $0.01733 |
| Sonnet 5 | $0.00016 | $0.00693 |
| Haiku 4.5 | $0.00008 | $0.00347 |
Grade A, and why
grill-me-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 13d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grill Me QA
A guided, systematic interview that challenges every aspect of a QA automation plan or test strategy until all decisions are resolved. Designed for QA Automation Engineers, SDETs, and QA Leads working with AI-assisted testing tools.
Activation: Triggered when the user wants to validate, challenge, or stress-test a testing plan, test strategy, framework choice, test architecture, or AI-testing strategy. Also activated by explicit reference: "use the skill grill-me-qa".
When to Use This Skill
- Before starting a new test automation project or framework
- When adopting AI tools for test generation, healing, or analysis
- Before presenting a test strategy to stakeholders
- When refactoring or migrating an existing test suite
- When evaluating tool/framework trade-offs (Playwright vs Selenium vs Cypress vs k6)
- Before scaling test coverage or reorganizing a regression suite
- When flaky tests are undermining trust in the suite
Trigger Phrases
The skill activates on explicit requests and on implicit intent. Treat these as activation signals in both English and Spanish:
- "grill my test plan", "audit my QA automation framework", "challenge my QA strategy"
- "challenge my testing decisions", "review my test architecture"
- "should I use Playwright or Cypress?", "how should I structure my tests?"
- "my tests are flaky, help me figure out why"
- "migrate from Selenium to Playwright", "is my test pyramid healthy?"
- "how do I set up quality gates?", "why is my test suite so slow?"
- "revisa mi estrategia de pruebas", "audita mi plan de QA"
- "audita mi framework de automatización", "pon a prueba mi framework de automatización"
- "mis tests son flaky", "revisa mi arquitectura de pruebas"
When NOT to Use This Skill
This skill grills strategy and architecture decisions. It is not the right tool for:
- Writing or debugging a single test → use
playwright-e2e-testing,api-testing, or the relevant framework skill - Generic code review of production (non-test) code
- Fixing one isolated failing test (that is debugging, not strategy)
What ships with it
5 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.
- 13d ago First seen · 225 lines · 81 tokens per session scan A 6c1075ec370a
grill-me-qa is a skill published in the GitHub repository fugazi/test-automation-skills-agents (234 stars, last pushed 9d ago), licensed MIT. It adds 81 tokens to every session and 3,467 once invoked, about $0.0004 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-30.
Other skills, from other repositories
unit-test
A Go testing workflow for writing unit tests: small tests that check individual functions or components. It supports table-driven cases, where many inputs and expected results are organised in one test, and subtests.
api-integration-test
Create, maintain, and run gated Go integration tests for internal APIs and service-to-service clients (HTTP/gRPC). Use for endpoint verification, contract checks with real runtime config, opt-in execution, timeout/retry safety, and integration failure triage in Go services.
load-test
Performance load testing specialist for writing k6/vegeta/wrk scripts, defining SLOs, modeling scenarios (spike/soak/stress/breakpoint), analyzing results, and identifying bottlenecks. ALWAYS use when writing load test scripts, reviewing test results, designing test scenarios, setting performance SLOs, or diagnosing…
e2e-test
Design, maintain, and execute reliable end-to-end tests for critical user journeys with Agent Browser as first choice for exploration and Playwright as the preferred code path for suites and CI. Use for E2E strategy, journey coverage, flaky test triage, artifact collection, CI gating, regression prevention, and…
fuzzing-test
A Go testing guide for generating fuzz tests, which repeatedly try varied inputs to find crashes and unexpected behavior. It first checks whether the code is suitable for fuzzing.
tdd-workflow
Enforce practical Test-Driven Development for code changes in Go services. Use for new features, bug fixes, refactors, API changes, and new modules. Requires Red-Green-Refactor evidence, defect-hypothesis-driven tests, killer cases, and coverage gates (line + risk-path).