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/jpoutrin/product-forgenpx agentmods add skills/jpoutrin/product-forge/enrich-qa-testWrote 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/enrich-qa-test)<a href="https://agentmods.dev/skills/jpoutrin/product-forge/enrich-qa-test"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/enrich-qa-test/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/enrich-qa-test"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/enrich-qa-test.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.00016 | $0.01660 |
| Opus 5 | $0.00008 | $0.00830 |
| Sonnet 5 | $0.00003 | $0.00332 |
| Haiku 4.5 | $0.00002 | $0.00166 |
Grade A, and why
enrich-qa-test 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 5d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
enrich-qa-test
Category: Quality Assurance
Usage
enrich-qa-test <qa-test-file> [--url <url>] [--update] [--elements-only]
Arguments
<qa-test-file>: Required - Path to the QA test procedure file (e.g.,qa-tests/active/QA-20250105-001-login.md)--url: Optional - Override the test URL from the document--update: Optional - Automatically update the QA test file with screenshots--elements-only: Optional - Only capture element screenshots, skip full-page captures
Purpose
This command reviews an existing QA test procedure, identifies UI elements mentioned in test steps, captures targeted screenshots of each element using Playwright, and enriches the documentation with visual references.
Execution Instructions for Claude Code
When this command is run, Claude Code should:
Phase 1: Parse QA Test Document
-
Read the QA test file
- Extract metadata (Test ID, URL, feature name)
- Parse all test cases (TC-###) and edge cases (EC-###)
-
Extract element references from test steps
- Scan for bold text: Element Name
- Scan for quoted elements: "Element Name"
- Identify action + element patterns:
- "Click the Login button"
- "Enter text in the Email field"
- "Select from the Country dropdown"
-
Build element extraction list
Elements found in QA-20250105-001-login.md: TC-001: - Step 2: Email field (input) - Step 3: Password field (input) - Step 4: Login button (button) TC-002: - Step 1: Forgot password link (link)
Phase 2: Capture Screenshots
-
Navigate to test URL using Playwright MCP
browser_navigate → {url from metadata or --url} -
Take initial full-page snapshot
browser_snapshot → understand page structure browser_take_screenshot → screenshots/{test-id}/00-initial-state.png -
For each identified element:
- Locate element using accessibility tree or selectors
- Capture element screenshot
- Save to
screenshots/{test-id}/elements/{element-name}.png
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.
- 5d ago First seen · 233 lines · 16 tokens per session scan A 2778b525c980
enrich-qa-test is a skill published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 1,660 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…