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 jpoutrin/product-forge --skill list-qa-testsgit clone --depth 1 https://github.com/jpoutrin/product-forgeWrote 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/jpoutrin/product-forge/list-qa-tests)<a href="https://agentmods.dev/skills/jpoutrin/product-forge/list-qa-tests"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/list-qa-tests/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/jpoutrin/product-forge/list-qa-tests"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/list-qa-tests.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.00013 | $0.01376 |
| Opus 5.5 | $0.00005 | $0.00550 |
| Sonnet 5.5 | $0.00003 | $0.00275 |
| Haiku 4.5 | $0.00001 | $0.00138 |
Grade A, and why
list-qa-tests 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.
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
list-qa-tests
Category: Quality Assurance
Usage
list-qa-tests [--status <status>] [--priority <priority>] [--format <format>]
Arguments
--status: Optional - Filter by status (draft, active, executed, archived)--priority: Optional - Filter by priority (critical, high, medium, low)--format: Optional - Output format (table, list, json). Default: table
Execution Instructions for Claude Code
When this command is run, Claude Code should:
-
Scan QA Test Directories
qa-tests/ ├── draft/ → Status: DRAFT ├── active/ → Status: ACTIVE ├── executed/ → Status: EXECUTED └── archived/ → Status: ARCHIVED -
Parse Each QA Test File
- Extract metadata from markdown header
- Read: Test ID, Feature, Priority, Status, Estimated Time
- Count test cases (TC-###) and edge cases (EC-###)
-
Apply Filters
- Filter by status if
--statusprovided - Filter by priority if
--priorityprovided
- Filter by status if
-
Calculate Metrics
- For executed tests: Extract last execution result
- Count total tests per status
- Count by priority
-
Format and Display Results
- Sort by priority (critical first), then by date
Output Formats
Table Format (default)
QA Tests - Found 8 tests
Status | Priority | Test ID | Feature | Cases | Last Run | Result
---------|----------|----------------------|----------------|-------|------------|--------
ACTIVE | Critical | QA-20250105-001 | user-login | 5 | - | -
ACTIVE | High | QA-20250104-002 | checkout | 8 | - | -
EXECUTED | Critical | QA-20250103-001 | payment | 6 | 2025-01-04 | PASS
EXECUTED | Medium | QA-20250102-003 | search | 4 | 2025-01-03 | FAIL
DRAFT | Low | QA-20250105-002 | preferences | 2 | - | -
Summary:
- Draft: 1 | Active: 2 | Executed: 2 | Archived: 0
- Critical: 2 | High: 1 | Medium: 1 | Low: 1
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 · 194 lines · 13 tokens per session scan A 5b85ed509d97
list-qa-tests is a skill published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 1,376 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.