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 arvoreeducacao/rhm --skill qa-testinggit clone --depth 1 https://github.com/arvoreeducacao/rhmWrote 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/arvoreeducacao/rhm/qa-testing)<a href="https://agentmods.dev/skills/arvoreeducacao/rhm/qa-testing"><img src="https://agentmods.dev/badge/skills/arvoreeducacao/rhm/qa-testing/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/arvoreeducacao/rhm/qa-testing"><img src="https://agentmods.dev/badge/skills/arvoreeducacao/rhm/qa-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 29 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00047 | $0.00364 |
| Opus 5.5 | $0.00019 | $0.00146 |
| Sonnet 5.5 | $0.00009 | $0.00073 |
| Haiku 4.5 | $0.00005 | $0.00036 |
Grade A, and why
qa-testing scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: QA and testing knowledge. Use when testing an implementation end-to-end — building a test plan, validating APIs with curl, driving the UI with Playwright, comparing against Figma, and documenting pass/fail w What it actually says
QA Testing
Use this skill when validating an implementation across any affected layer (backend APIs and/or frontend UI).
Approach
- Identify all test cases from the requirements (happy path, edge cases, errors, UI flows, interactions)
- Start the affected services if not running
- Test backend cases using curl, scripts, or API calls
- Test frontend cases using Playwright (browser automation)
- Compare UI with Figma designs if available
- Document pass/fail with evidence (screenshots when relevant)
Tools
- curl for API validation
- database MCPs to verify data state after operations
- Playwright MCP for browser-based testing
- Figma MCP to compare implementation with design
Security
- Never access tokens or credentials directly from the database
- Use environment variables for test user tokens
- Never include tokens or secrets in documents or output
Documenting results
Separate results by repository:
### Repository: api
#### Test: Create user profile
- Status: PASS
- Evidence: 201 response with expected payload
### Repository: frontend
#### Test: Form validation on submit
- Status: FAIL
- Evidence: Email field accepts invalid format
- Expected: Inline validation error
If you need the user to do something (DB changes, restart services), document it clearly, continue with independent tests, and mark dependent tests as waiting.
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 · 51 lines · 47 tokens per session scan A 0c8138164e14
qa-testing is a skill published in the GitHub repository arvoreeducacao/rhm (19 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 364 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
critique
Adversarial design critique of the current work — render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.