Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/dayvisonassis/sdd-skillsnpx agentmods add skills/dayvisonassis/sdd-skills/qa-preflightWrote 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/dayvisonassis/sdd-skills/qa-preflight)<a href="https://agentmods.dev/skills/dayvisonassis/sdd-skills/qa-preflight"><img src="https://agentmods.dev/badge/skills/dayvisonassis/sdd-skills/qa-preflight/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/dayvisonassis/sdd-skills/qa-preflight"><img src="https://agentmods.dev/badge/skills/dayvisonassis/sdd-skills/qa-preflight.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.00101 | $0.04815 |
| Opus 5.5 | $0.00040 | $0.01926 |
| Sonnet 5.5 | $0.00020 | $0.00963 |
| Haiku 4.5 | $0.00010 | $0.00481 |
Grade A, and why
qa-preflight 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 16d 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 — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Preflight
A gate, not a plan generator. A plan generator moves work onto the human; this removes work from the human and uses what remains as the definition of what actually needs a person.
References, loaded on demand:
references/qa-practices.md(how cases are derived) andreferences/report-template.md(the exact output skeletons). Both travel with this skill, so both resolve wherever it is installed.The rationale — why each rule exists and what this skill deliberately does NOT do — is in
docs/Skill_QA_Preflight.mdof the sdd-skills repository, which is where the skill is maintained. That file is not part of an installed copy, and the relative path this note used to give (../../docs/) resolved to nothing outside the source repository. Everything needed to RUN the skill is in the folder you are reading; go to the rationale only to change a rule, and change it there.
Standalone by decision. No other skill invokes this one. It runs when the feature is done, on explicit human request. Running it mid-implementation produces noise about code that is still moving.
It owns no correction logic. Defects are fixed by dispatching the correctors that already exist, with the discipline they already have.
One carve-out, and only one: the visual guard. A permanent guard that is a test goes to
the matching test-writer — a guard for a user flow goes to e2e-test-writer when the
project has an e2e suite (GATES.md lists an e2e gate proven green). A guard that is a gate
rule stays a proposal in the findings report: building gates is gate-builder's job. The
exception is a computed-value assertion (contrast, height, density): no test-writer covers
the visual suite, so when the visual gate is enabled the skill writes that assertion itself.
This is guard code, not product behaviour — it changes what is checked, never what the
application does. Production code stays off-limits under every circumstance, and the guard
still goes through the checkpoint like any other change.
What ships with it
2 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.
- 16d ago Changed · +29 lines e940acb42f97
- 18d ago Changed · +2 lines d6ad75bee460
- 1mo ago Changed · +26 lines c9bb7d9a24f0
- 2mo ago First seen · 304 lines · 101 tokens per session scan A ae9509ec97d2
qa-preflight is a skill published in the GitHub repository dayvisonassis/sdd-skills (3 stars, last pushed 16d ago), licensed MIT. It adds 101 tokens to every session and 4,815 once invoked, about $0.0004 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
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
critique
Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.
ship
Pre-release gate. Run the full gate, responsive + render checks, then produce the release checklist (README badge/current/changelog). Use before tagging a release.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
ai-eval-plan
Design an evaluation plan for an LLM or AI feature before shipping it. Use when asked how to evaluate a prompt/model/agent, set up an eval harness, define quality metrics for an AI feature, or build a regression gate. Produces an eval plan — task definition, datasets, metrics & rubrics, baselines, automated + human…
browser-test-loop
Use to actually verify a web change in a real browser instead of assuming it works — click through a flow, catch console errors, check a form submits, confirm a fix on the page. Trigger when a UI change needs proof, a bug only reproduces in the browser, or the user asks to test, check, or screenshot the running app.