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 evgenii-studitskikh/Claude-Code-SaaS-Studio --skill qa-plangit clone --depth 1 https://github.com/evgenii-studitskikh/Claude-Code-SaaS-StudioWrote 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/evgenii-studitskikh/claude-code-saas-studio/qa-plan)<a href="https://agentmods.dev/skills/evgenii-studitskikh/claude-code-saas-studio/qa-plan"><img src="https://agentmods.dev/badge/skills/evgenii-studitskikh/claude-code-saas-studio/qa-plan/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/evgenii-studitskikh/claude-code-saas-studio/qa-plan"><img src="https://agentmods.dev/badge/skills/evgenii-studitskikh/claude-code-saas-studio/qa-plan.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.00049 | $0.00391 |
| Opus 5.5 | $0.00020 | $0.00156 |
| Sonnet 5.5 | $0.00010 | $0.00078 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
qa-plan 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 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.
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.
What it actually says
Decide how this SaaS will be tested before scaffolding or writing any tests. Non-autonomous: ask first, present options, get sign-off.
Phases
- Load context — read
docs/specs/prd.md,docs/specs/architecture.md, anddocs/specs/data-model.mdif present, to learn the features and the tenant model. If the PRD is missing, stop and direct to/write-prd. - Choose the pyramid — propose how much unit vs. integration vs. e2e, and the tools (Vitest + Testing Library, Playwright, Stripe-signed test payloads, Supabase RLS tests). Present 2–3 options with trade-offs.
- Identify critical seams — list the must-test risk areas: tenant isolation (RLS), auth/session, billing webhooks, input validation boundaries.
- Draft the plan — fill
.claude/templates/qa-plan.mdintodocs/specs/qa-plan.md(draft, await approval). Honor the review intensity: underfull, confirm each section; underlean, one confirmation before writing; undersolo, write then summarize. - Next step — on approval, point to
/test-setup.
Output
docs/specs/qa-plan.md. Writes nothing else without approval.
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 · 22 lines · 49 tokens per session scan A cd8dc2e5b2e3
qa-plan is a skill published in the GitHub repository evgenii-studitskikh/Claude-Code-SaaS-Studio (2 stars, last pushed 4mo ago), licensed MIT. It adds 49 tokens to every session and 391 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-08-31.
Other skills, from other repositories
feature-loop
Coding agent for the project-level harness — one feature per session, must verify, must be mergeable.
ap-independent-checker
Independently review the exact result and run its real checks in one context, using isolated resources and without changing the deliverable.
ap-execharness-resolver
Report the compatibility redirect to ap-worker; this retired role cannot perform new work.
ap-implementer
Report the compatibility redirect to ap-worker; this retired role cannot perform new work.
repo-harness-check
Plan scoped harness work, review a plan, or assess recorded checks and risk. Do not execute implementation or publish by default.
oak-runtime-verification
Use after tests and validation pass and before the final review, whenever a change could show up at runtime - a screen, a command, an endpoint, a job or a data store - to prove the change works in the running system, including its failure path, with repeatable steps and minimal evidence.