Borrowing it
Nothing to install: this file belongs to compozy/skeeper. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/compozy/skeeper/main/.agents/skills/qa-execution/SKILL.mdgit clone --depth 1 https://github.com/compozy/skeeperWrote 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/compozy/skeeper/qa-execution)<a href="https://agentmods.dev/skills/compozy/skeeper/qa-execution"><img src="https://agentmods.dev/badge/skills/compozy/skeeper/qa-execution/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/compozy/skeeper/qa-execution"><img src="https://agentmods.dev/badge/skills/compozy/skeeper/qa-execution.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.00140 | $0.02771 |
| Opus 5.5 | $0.00056 | $0.01108 |
| Sonnet 5.5 | $0.00028 | $0.00554 |
| Haiku 4.5 | $0.00014 | $0.00277 |
Grade A, and why
qa-execution 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
5. When the project has a Web UI surface, start the dev server in the background using the discovered start command. Confirm readiness by waiting for the server to respond (e.g., `curl -sf -o /dev/null http://localhost:< Copies of this mod
1 near-identical copy found in the catalogue:
- rc-qa-execution — 89% identical, 10 lines differ
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systematic Project QA
Required Inputs
- qa-output-path (optional): Directory where QA artifacts (issues, screenshots, verification reports) are stored. When provided, create the directory if it does not exist and use it for all QA outputs. When omitted, fall back to repository conventions or
/tmp/codex-qa-<slug>.
Procedures
Step 1: Discover the Repository QA Contract
- Read root instructions, repository docs, and CI/build files before running commands.
- Execute
python3 scripts/discover-project-contract.py --root .to surface candidate install, verify, build, test, lint, start commands, Web UI signals, and E2E signals. - Read
references/project-signals.mdwhen command ownership is ambiguous or when multiple ecosystems are present. - Read
references/e2e-coverage.mdto decide whether the repository already supports public-surface automated coverage and how strong that support is. - Prefer repository-defined umbrella commands such as
make verify,just verify, or CI entrypoints over language-default commands. - Identify the changed surface and the regression-critical surface before choosing scenarios.
- Determine whether the project has a Web UI surface. Indicators include: a
startordevcommand that launches a web server, framework config files (next.config.*,vite.config.*,nuxt.config.*,angular.json,svelte.config.*), or HTML/template entry points. Record the dev server URL (defaulthttp://localhost:3000unless the project specifies otherwise). - Record the E2E contract in working notes: support detected or not, harness name, canonical command, known spec locations, and blockers.
- Resolve the QA artifact directory. If the user provided a
qa-output-pathargument, use that path. Otherwise, use repository conventions. If neither exists, fall back to/tmp/codex-qa-<slug>. Create theqa/subdirectory under the resolved path if it does not exist. Store all issues, screenshots, and verification reports under<qa-output-path>/qa/.
What ships with it
7 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.
- 1mo ago First seen · 111 lines · 140 tokens per session scan A 606a7ff5443e
qa-execution is a skill published in the GitHub repository compozy/skeeper (89 stars, last pushed 4mo ago), licensed MIT. It adds 140 tokens to every session and 2,771 once invoked, about $0.0006 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
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.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
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…
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.
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.
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.