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 lsantosweb/codex-agents-skills-kit --skill qa-automation-engineergit clone --depth 1 https://github.com/lsantosweb/codex-agents-skills-kitWrote 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/lsantosweb/codex-agents-skills-kit/qa-automation-engineer)<a href="https://agentmods.dev/skills/lsantosweb/codex-agents-skills-kit/qa-automation-engineer"><img src="https://agentmods.dev/badge/skills/lsantosweb/codex-agents-skills-kit/qa-automation-engineer.svg" alt="Measured on agentmods" 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.00034 | $0.00371 |
| Opus 5 | $0.00017 | $0.00186 |
| Sonnet 5 | $0.00007 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
qa-automation-engineer 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 8d 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.
What it actually says
When to use
Use this skill for:
- Playwright or Cypress setup
- end-to-end testing of critical flows
- CI test pipeline setup
- regression suites
- visual regression
- reproducing bugs through automation
- investigating flaky tests
Core operating rules
- If it is not automated, it is not protected.
- Prefer stable assertions over sleep-based waiting.
- Test the unhappy path, not just the happy path.
- Isolate test data per scenario whenever possible.
- Keep smoke tests fast and regression tests deeper.
- Page objects or equivalent abstractions are preferred for reusable flows.
Testing priorities
Smoke suite
- login or auth entry
- primary user flow
- one business-critical transaction
Regression suite
- edge cases
- error states
- permission boundaries
- cross-browser or device coverage when relevant
Destructive scenarios
- slow network
- 500 responses
- rage clicks / duplicate submission
- session expiry mid-flow
- bad input or injection attempts
Workflow
- Identify the highest-risk user journeys.
- Define what belongs in smoke vs regression.
- Implement tests with deterministic waits.
- Wire tests into CI when requested.
- Report failures with reproduction context.
Mandatory checks
- no arbitrary sleeps when an explicit assertion can be used
- selectors are resilient
- tests do not depend on previous test state
- CI command is documented if pipeline work is included
Output format
Report:
- flows covered
- framework chosen and why
- files changed
- how to run tests locally and in CI
- remaining coverage gaps
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.
- 8d ago First seen · 69 lines · 34 tokens per session scan A 2162fe11474f
qa-automation-engineer is a skill published in the GitHub repository lsantosweb/codex-agents-skills-kit (2 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 371 once invoked, about $0.0002 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
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…