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 majiayu000/spellbook --skill agent-qa-testinggit clone --depth 1 https://github.com/majiayu000/spellbookWrote 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/majiayu000/spellbook/agent-qa-testing)<a href="https://agentmods.dev/skills/majiayu000/spellbook/agent-qa-testing"><img src="https://agentmods.dev/badge/skills/majiayu000/spellbook/agent-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/majiayu000/spellbook/agent-qa-testing"><img src="https://agentmods.dev/badge/skills/majiayu000/spellbook/agent-qa-testing.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.00056 | $0.01361 |
| Opus 5.5 | $0.00022 | $0.00544 |
| Sonnet 5.5 | $0.00011 | $0.00272 |
| Haiku 4.5 | $0.00006 | $0.00136 |
Grade A, and why
agent-qa-testing 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 3d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-qa testing
Use agent-qa for web, Android, and iOS regression tests with advanced memidex memory and self-improvement. Work with the project's existing tests, targets, and model configuration.
When to Use
- Validate or run a selected agent-qa regression test in an initialized project.
- Investigate a failed or healed agent-qa run using recorded evidence.
- Inspect the memidex knowledge associated with that run.
This is a product-verification skill for an existing agent-qa workflow. For a whole-app feature inventory and user-story tracker, use app-user-story-qa.
Operating Contract
Direct actions: Inspect configuration and recorded evidence, validate YAML, and perform dry runs within the requested workspace. Run application tests only against the user-authorized target and data.
Escalate before: Production actions, paid execution, credential changes, or scope expansion unless the user has already explicitly authorized them.
A testing request does not authorize application repairs. Preserve failures and propose an evidence-based fix unless the user has also requested changes.
Evidence-backed pushback: If a request broadens execution beyond the configured target, cite that mismatch and propose a scoped dry run until the target is resolved.
Feedback loop: When a setup or triage mistake recurs, record the verified symptom and correction in the project's existing QA notes, with secrets removed; use that evidence to improve the next run.
Core Process
1. Establish the test scope
- Locate
agent-qa.config.yamland the requested test or suite. Run from that project directory; a global--config <path>must appear before the command. - Use the project's installed version and package manager. The examples below assume an npm installation and use
--no-installto avoid downloading a different version. Replacetests/checkout.yamlwith the selected test path. - agent-qa requires Node.js 24+. If it is not installed or initialized, use the official quickstart and the user's chosen provider; preserve existing configuration and credentials.
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.
- 3d ago First seen · 105 lines · 56 tokens per session scan A 8e192e5b3b98
agent-qa-testing is a skill published in the GitHub repository majiayu000/spellbook (288 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 1,361 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-10-27.
Other skills, from other repositories
integration-e2e-testing
Defines integration/E2E skeleton annotations, lane and file contracts, and route-parity review criteria. Use when generating or consuming test skeletons or reviewing shared mutation routes.
recipe-add-integration-tests
Add integration/E2E tests to existing codebase using Design Docs.
integration-e2e-testing
Selects and designs the smallest integration/E2E test set that proves accepted behavior at an observable boundary. Use when writing or reviewing E2E or integration tests.
tuturuuu-cli-resources
Queue heavy local Tuturuuu validation and diagnose competing CPU or RAM workloads with ttr resources.
frontend-typescript-testing
Designs frontend tests using the repository's configured React test and browser harnesses, including RTL, MSW, Vitest, and Playwright when present. Use when adding or reviewing component, loading/error-state, integration, or frontend E2E tests.
visual-proof
Capture before/after screenshot evidence of a web page at real breakpoints (375, 768, 1440) in both light and dark themes, using Playwright against a local dev server or a deployed URL. Use before starting any visual change to capture the current state, and again after to prove the delta. Also use when asked to "show…