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.03654 |
| Opus 5 | $0.00051 | $0.01827 |
| Sonnet 5 | $0.00020 | $0.00731 |
| Haiku 4.5 | $0.00010 | $0.00365 |
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 9d 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 — 304 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 permanent guard. No test-writer covers a browser-level assertion 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.
INPUT
- Target feature (ID, e.g.
F08). - Auto-discovers: the feature's
spec.md/plan.md/contract.md, its PRD section,progress.json, the routes and permission blocks it added, and its diff against the integration branch. - Reads the project's design-system skill when one exists (for the numeric values the
accessibility axis asserts). Without it, the accessibility axis falls back to the generic
WCAG floors in
references/qa-practices.md.
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.
- 9d 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 (1 stars, last pushed 12d ago), licensed MIT. It adds 101 tokens to every session and 3,654 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
test-first-bugs
Enforces a test-driven bug-fixing workflow. Use when a user reports a bug, failing code, an error, or asks to fix something.
702-technologies-wiremock
Use when you need framework-agnostic WireMock guidance — stub design, JSON or programmatic mappings, precise request matching, response bodies and faults, classpath fixtures, isolation and reset between tests, verification of calls, dynamic ports and base URLs, and avoiding flaky stubs — without choosing Spring Boot…
coverage-enhancer
Analyze existing test suites and source code to suggest additional unit tests that improve test coverage. Use this skill when working with test files and source code to identify untested code paths, missing edge cases, uncovered branches, untested error conditions, and gaps in test coverage. Supports major testing…
321-frameworks-spring-boot-testing-unit-tests
Use when you need to write unit tests for Spring Boot applications — including pure unit tests with @ExtendWith(MockitoExtension.class) for @Service/@Component, slice tests with @WebMvcTest and @MockitoBean for controllers, @JsonTest for JSON serialization, parameterized tests with @CsvSource/@MethodSource, test…
322-frameworks-spring-boot-testing-integration-tests
Use when you need to write or improve integration tests — including Testcontainers with @ServiceConnection, @DataJdbcTest persistence slices, TestRestTemplate or MockMvcTester for HTTP, data isolation, and container lifecycle management for Spring Boot 4.0.x. This should trigger for requests such as Review Java code…