Borrowing it
Nothing to install: this file belongs to sumithr/sumo-qa. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sumithr/sumo-qa/main/.claude/skills/scaffold-sumo-qa-skill/SKILL.mdgit clone --depth 1 https://github.com/sumithr/sumo-qaWrote 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/sumithr/sumo-qa/scaffold-sumo-qa-skill)<a href="https://agentmods.dev/skills/sumithr/sumo-qa/scaffold-sumo-qa-skill"><img src="https://agentmods.dev/badge/skills/sumithr/sumo-qa/scaffold-sumo-qa-skill.svg" alt="Measured on agentmods" 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.00138 | $0.01219 |
| Opus 5 | $0.00069 | $0.00609 |
| Sonnet 5 | $0.00028 | $0.00244 |
| Haiku 4.5 | $0.00014 | $0.00122 |
Grade A, and why
scaffold-sumo-qa-skill 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 8d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
scaffold-sumo-qa-skill
Drives the four-step recipe for adding a new sumo-qa-<name> sub-skill so all the pieces land together. The deterministic file generation lives in scripts/scaffold.py; this document is the thin guide for gathering inputs and checking the surfaces the script cannot reach (the installed MCP server).
When to use
Trigger this skill whenever the user asks to add a new sumo-qa sub-skill — phrases like "scaffold a new skill", "add a sumo-qa-X skill", "I want a skill that handles Y for QA", or even just "let's start the routing for Z". The user invokes it explicitly with /scaffold-sumo-qa-skill; it doesn't auto-trigger.
Inputs
Gather these from the user up front. If they only give a partial set, ask for the rest in one round of questions — don't drip-feed.
- Skill name (without prefix) — kebab-case, descriptive of the user-intent the skill handles. The script prepends
sumo-qa-automatically. - One-line description — for the SKILL.md frontmatter
description:. Convention across the estate: start with "Use when ..." so the trigger context is obvious. - Approach tag — the kebab-case routing key that lands in
knowledge/approaches.md. The user'ssumo-qa-deciding-approachskill consults this catalogue when picking which sub-skill to route to.
Verify the surfaces the script can't reach
The script checks for collisions against the source tree (skills/, tests/evals/promptfoo/, knowledge/approaches.md). It can't check the installed MCP server, which serves a frozen-at-install-time view of the catalogues. Before invoking the script, call:
sumo_qa_load_approaches
through the MCP server and confirm the proposed approach tag isn't already shipped. The source tree may have unreleased entries the MCP doesn't yet see, and vice versa — checking both surfaces is what catches both classes of collision.
Run the script
python3 .claude/skills/scaffold-sumo-qa-skill/scripts/scaffold.py \
--name <kebab-name> \
--description "Use when <triggering context>." \
--approach-tag <kebab-tag>
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.
- 8d ago First seen · 61 lines · 138 tokens per session scan A e136bff42662
scaffold-sumo-qa-skill is a skill published in the GitHub repository sumithr/sumo-qa (6 stars, last pushed today), licensed Apache-2.0. It adds 138 tokens to every session and 1,219 once invoked, about $0.0007 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
live-audit
Audit steam-games-mcp — build/test/lint gate, live MCP tool edge-case sweep (input validation, SteamID64/vanity/appid edge cases, key-gating), and source-level code review. Use when asked to test/audit the published or just-fixed steam-games-mcp package, hunt for bugs/edge cases, or repeat "the same kind of testing as…
pr-quality-cycle
Combined PR quality workflow: address inline review comments AND fix Codecov patch coverage gaps in one end-to-end cycle. Use when a PR has both review feedback and coverage regression, or when you want a single checklist that covers triage, code fixes, test additions, verification, and push-gate validation before…
qa
QA test a live website with Axon discovery/content evidence plus browser automation when interaction is required. Use when the user wants exploratory QA, form testing, navigation/link checks, responsive checks, performance observations, bug reports, or a pre-launch quality review.
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.