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 dean0x/devflow --skill qagit clone --depth 1 https://github.com/dean0x/devflowWrote 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/dean0x/devflow/qa)<a href="https://agentmods.dev/skills/dean0x/devflow/qa"><img src="https://agentmods.dev/badge/skills/dean0x/devflow/qa/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/dean0x/devflow/qa"><img src="https://agentmods.dev/badge/skills/dean0x/devflow/qa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00016 | $0.01363 |
| Opus 5.5 | $0.00006 | $0.00545 |
| Sonnet 5.5 | $0.00003 | $0.00273 |
| Haiku 4.5 | $0.00002 | $0.00136 |
Grade A, and why
qa scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| HTTP status | Response code from curl/fetch | API endpoints | How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Patterns
Scenario-based acceptance testing methodology. Ensures implementations satisfy user-observable requirements beyond what unit tests cover.
Iron Law
VERIFY BEHAVIOR FROM THE USER'S PERSPECTIVE [1][2]
Test what the user asked for, not implementation details. Every acceptance criterion gets at least one scenario. Every scenario produces observable evidence. If you can't demonstrate it works from the outside, it doesn't work. [3][8]
Scenario Types [1][2][6]
Five categories ensure comprehensive coverage:
| Type | Purpose | Example |
|---|---|---|
| Happy path | Core functionality works as described | "Add item → item appears in list" |
| Boundary/edge | Limits, empty, maximum, minimum values | "Add item with 1000-char name → truncated or rejected" |
| Negative path | Invalid inputs, missing permissions, errors | "Add item without auth → 401 returned" |
| Integration | Components work together correctly | "Add item → appears in search results" |
| Regression | Existing behavior preserved after changes | "Old items still load after schema migration" |
Minimum coverage: At least one scenario per acceptance criterion. At least one boundary and one negative scenario per feature. [1][6]
Scenario Design from Acceptance Criteria [4][8][9]
Extract testable claims using Given/When/Then:
Acceptance criterion: "Users can upload files up to 10MB"
S1 (happy): Given auth user, When upload 5MB file, Then 200 + file accessible
S2 (boundary): Given auth user, When upload 10MB file, Then 200 (exact limit)
S3 (boundary): Given auth user, When upload 10.1MB file, Then 413 rejected
S4 (negative): Given no auth, When upload 5MB file, Then 401
S5 (negative): Given auth user, When upload empty file, Then 400
Extracting criteria [4]: If no explicit acceptance criteria, derive from the request:
- What new behavior was requested? → happy path scenarios
- What inputs does it accept? → boundary scenarios [7][10]
- What should it reject? → negative scenarios
- What existing behavior must survive? → regression scenarios
What ships with it
5 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.
- 2d ago Changed 96908d4bf3bd
- 7d ago Changed · -2 lines · -15 tokens per session 5e878f576eb2
- 1mo ago First seen · 137 lines · 31 tokens per session scan A 4331908ca167
qa is a skill published in the GitHub repository dean0x/devflow (20 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 1,363 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
remove-ai-slops
Removes AI-generated code smells from branch changes or an explicit file list behind regression tests. Use when the user asks to clean up, deslop, or remove AI-slop patterns from recent changes.
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.
check
Auto-fix lint and formatting, then report types and tests. Run before every commit.
code-guidelines-go
Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…