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 TimothyHan/qa-buddy-skills --skill evalgit clone --depth 1 https://github.com/TimothyHan/qa-buddy-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/timothyhan/qa-buddy-skills/eval)<a href="https://agentmods.dev/skills/timothyhan/qa-buddy-skills/eval"><img src="https://agentmods.dev/badge/skills/timothyhan/qa-buddy-skills/eval.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
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 →
- medium MCP Rug Pull · line 32 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 119 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00130 | $0.02073 |
| Opus 5 | $0.00065 | $0.01037 |
| Sonnet 5 | $0.00026 | $0.00415 |
| Haiku 4.5 | $0.00013 | $0.00207 |
Grade A, and why
eval 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 7d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/qa-eval: Skill Eval Testing
You run eval fixtures against a skill to verify it produces correct output. Each fixture declares its mode:
simulate(default) — read the skill's instructions, simulate the scenario, check assertions against the hypothetical output. For skills whose output is prose (reports, verdicts, plans).execute— actually run the skill against the local fixture app, then grade the artifacts it produced by executing them (npx playwright test, greps, file checks). For skills whose output is code (/qa-e2e-setup,/qa-e2e-pom,/qa-e2e-write). A generated artifact passes only by running, never by looking right.
Constraints
- One skill at a time. Don't run all skills in one session — context window.
- Follow the skill's instructions exactly. When simulating or executing, you are that skill. Apply its constraints, phases, and methodology references.
- Grade honestly. If an assertion fails, report it — don't rationalize a pass.
- Assertions are literal.
contains "READY"means the string "READY" appears in the output. Don't interpret loosely. - Simulate mode never touches the real environment — no browsers, no Jira, no file writes.
- Execute mode touches ONLY the local fixture app and a scratch workspace. Never external systems: no Jira, no real staging URLs, no network beyond
localhost. All generated artifacts go in a throwaway workspace directory, never the QABuddy repo. - Never open
ANSWER-KEY.mdwhile acting as the skill under eval. The answer key is for grading only. Discovery must happen against the running app. Reading the key mid-simulation invalidates the fixture — report it as a harness error, not a pass. - Scripted user responses replace the user. Execute fixtures include
user_responsesfor the skill's interactive gates. Answer exactly as scripted. If the skill never asks at a gate where a response was scripted, that's a finding — several fixtures assert the skill does pause.
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.
- 7d ago First seen · 187 lines · 130 tokens per session scan A 1202194cfff0
eval is a skill published in the GitHub repository TimothyHan/qa-buddy-skills (7 stars, last pushed yesterday), licensed Apache-2.0. It adds 130 tokens to every session and 2,073 once invoked, about $0.0006 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-31.
Other skills, from other repositories
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; request automation of…
test-review
A review checklist for newly written or changed automated tests using TypeScript and Playwright. Playwright is a tool for testing web browsers, and automated tests check software without repeating the steps by hand.
playwright-expert
Expert in Playwright E2E testing framework, auto-waiting mechanisms, test generation, trace viewer, and CI/CD integration. Use when the user mentions testing, end-to-end tests, QA, automation, end-to-end testing, or test automation, or when the task involves Playwright Framework, Test Organization, Advanced Features…
test-cases
A tool for designing software test cases and exporting them as CSV files for Zephyr Scale, a test-management system, or creating them directly in a connected test-management tool.
testing
A thorough testing framework for websites, user interfaces, back-end services, APIs, and builds. It checks normal use, errors, limits, and unusual combinations, and records evidence for each result.
sniff
Use when the user types /sniff, or asks to "scan this project for bugs", "find bugs in my app", "QA my site", or "walk my app and tell me what's broken". For a running web app, finds real, reproducible issues (broken pages/links, console & network errors, broken forms, empty/placeholder data, state-loss, bad…