Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add victoraguilarsantamariadev/qa-explore/plugin install qa-exploreWrote 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/victoraguilarsantamariadev/qa-explore/qa-manual)<a href="https://agentmods.dev/skills/victoraguilarsantamariadev/qa-explore/qa-manual"><img src="https://agentmods.dev/badge/skills/victoraguilarsantamariadev/qa-explore/qa-manual/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/victoraguilarsantamariadev/qa-explore/qa-manual"><img src="https://agentmods.dev/badge/skills/victoraguilarsantamariadev/qa-explore/qa-manual.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.00158 | $0.01658 |
| Opus 5 | $0.00079 | $0.00829 |
| Sonnet 5 | $0.00032 | $0.00332 |
| Haiku 4.5 | $0.00016 | $0.00166 |
Grade A, and why
qa-manual 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 10d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
qa-manual
The same engine that drives your app to find bugs (qa-explore) can drive it to document it. Instead of a bug report, the output is a living manual: a coherent, screenshot-annotated guide walked in the order a real person would use the app.
recon the live app → ORDER the features as a real setup/usage sequence
→ propose a Table of Contents + AUDIENCE [GATE 1: you approve]
per section, in order: drive the app to that view → screenshot → annotate the steps
→ assemble ONE coherent Markdown manual (one clean example throughout)
→ draft ready [GATE 2: you review before it ships]
Markdown is the master → re-run when the UI drifts → docs update instead of rotting
What makes it a good manual (not a screenshot dump)
- Setup order, not file order. Dependencies/prerequisites first; each section builds on the previous. The recon step reorders whatever it discovers into the sequence a human actually follows.
- One coherent example throughout. The same clean sample data/flow runs across the whole manual, so screenshots tell a single story instead of contradicting each other.
- Audience is a knob. The same app yields an installer / configuration guide or an end-user / daily-use guide by setting
audience(which also reshapes the TOC and the depth of each step). - Every screenshot is annotated with what to do and what to notice — captured from the real app, never mocked.
- It won't document a broken flow. If a section's happy path hits a blocking bug, qa-manual flags it and leaves that section out (or marked "known issue") rather than teaching a broken path — run qa-explore/qa-fix first.
🔒 The two gates (never publish auto-docs blind)
- Approve the TOC + audience up front. The engine returns a proposed table of contents and audience; you edit/approve it before a single screenshot is taken. This is where you catch "wrong order", "wrong audience", "skip this section".
- Review the draft before it ships. The Markdown master is handed back for a human read before it becomes the published manual. Docs that go out unread are how wrong instructions reach users.
What ships with it
1 file 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.
- 10d ago First seen · 64 lines · 158 tokens per session scan A e67877bc00a7
qa-manual is a skill published in the GitHub repository victoraguilarsantamariadev/qa-explore (2 stars, last pushed 1mo ago), licensed MIT. It adds 158 tokens to every session and 1,658 once invoked, about $0.0008 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
generate-a11y-tests
Generates comprehensive Playwright accessibility tests with axe-core integration for any UI component or page. Use this skill to create automated accessibility regression tests that verify WCAG 2.1 Level AA compliance.\n\n \nContext: Developer has just completed building a login form component.\nuser: \"Generate…
link-purpose
Analyzes code for WCAG 2.4.4 Link Purpose (In Context) compliance. Identifies generic link text, ambiguous links, and links without sufficient context. Recommends descriptive link text and proper ARIA attributes.
accessible-dev
A development assistant that enforces accessibility-first coding practices during code generation. Use this skill when writing new UI components, features, or interfaces to ensure WCAG 2.1 Level AA compliance from the start.\n\n \nContext: Developer is building a new user registration form for a web…
contrast-checker
Color contrast analyzer for WCAG compliance. Use when analyzing color contrast in code files, when user mentions WCAG compliance, color accessibility, contrast ratios, or when discussing colors in UI components. Calculates contrast ratios, identifies violations, and suggests accessible color alternatives that preserve…
use-of-color
Analyzes code for WCAG 1.4.1 Use of Color compliance. Identifies where color is used as the only means of conveying information and recommends additional visual indicators like text, icons, patterns, or ARIA attributes.
refactor
Accessibility refactoring specialist. Automatically fixes accessibility issues across multiple files. Performs complex refactoring like extracting accessible components, restructuring markup, and implementing proper ARIA patterns.