Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Jarroslav/agentic-os/plugin install agentic-sdlcWrote 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/jarroslav/agentic-os/qa-e2e-generator)<a href="https://agentmods.dev/skills/jarroslav/agentic-os/qa-e2e-generator"><img src="https://agentmods.dev/badge/skills/jarroslav/agentic-os/qa-e2e-generator/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/jarroslav/agentic-os/qa-e2e-generator"><img src="https://agentmods.dev/badge/skills/jarroslav/agentic-os/qa-e2e-generator.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.00181 | $0.03917 |
| Opus 5.5 | $0.00072 | $0.01567 |
| Sonnet 5.5 | $0.00036 | $0.00783 |
| Haiku 4.5 | $0.00018 | $0.00392 |
Grade A, and why
qa-e2e-generator 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 2mo 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 — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
qa-e2e-generator
Orchestrator skill. One ticket id in, executable E2E automation out. You run an 11-phase pipeline that alternates inline shell steps with seven isolated subagent dispatches, each returning a structured verdict and writing its artifact to disk. Every completed phase is appended to a run ledger, so the flow is resumable.
Scope is the top of the test pyramid only — UI-level and API-level E2E. Unit-test generation is out of scope. Do not auto-invoke from the main SDLC orchestrator; a human (or a QA workflow) starts this explicitly.
Methodology owner. How automated scripts are structured and scoped is defined by the
test-scriptsblueprint inagentic-qe(skills/qe-blueprints/references/catalog/build/test-scripts.md). This skill executes; the blueprint is the authority on method. If the two ever disagree, the blueprint wins and this file is what gets corrected — one source of truth, so two agents cannot follow two different sets of practices.
Invocation
qa-e2e-generator PROJ-123
Exactly one argument: the ticket id. Missing it, halt with:
Usage: qa-e2e-generator <TICKET-ID>
Inputs
| Input | Source | Notes |
|---|---|---|
| Ticket id | CLI arg (e.g. PROJ-123) |
Required. Drives run slug + branch name. |
| Ticket adapter | .agentic/guides/project.md → ## Work Item Adapter |
Must be configured. Never a hardcoded backend. |
| QA strategy | .agentic/guides/testing/qa-strategy.md |
Produced by the QA-foundation skill. |
| Git conventions | .agentic/guides/standards/git-workflow.md |
Branch/commit rules for workspace setup. |
| Test env URL + auth | Asked at the env-config gate | Written with actual values, never placeholders. |
Output
Run root:
docs/superpowers/qa-tasks/<date>-<slug>/e2e/
where <date> = date +%Y-%m-%d and <slug> = lowercased ticket id. Treat
$RUN_DIR = docs/superpowers/qa-tasks/<date>-<slug>; all artifacts land under
$RUN_DIR/e2e/.
| Artifact | Written by | Purpose |
|---|---|---|
$RUN_DIR/e2e/events.jsonl |
every phase | Run ledger; resume source of truth. |
$RUN_DIR/e2e/ac-check.json |
Phase 2 | Normalized AC + confidence. |
$RUN_DIR/e2e/context-manifest.json |
Phase 3 | Feature area + repo topology. |
$RUN_DIR/e2e/complexity-assessment.json |
Phase 4 | Sizing / routing signal. |
$RUN_DIR/e2e/test-plan.md |
Phase 5 | Scenario-level suite plan. |
$RUN_DIR/e2e/env-config.json |
Phase 6 | Real target env + auth wiring. |
$RUN_DIR/e2e/execution-results.json |
Phase 8 | First-run pass/fail evidence. |
| test spec files | Phase 7 | The generated E2E suite (in the target repo). |
What ships with it
11 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.
- evals/evals.json 8.5 KB
- README.md 3.6 KB
- references/subagents/ac-check.md 7.9 KB
- references/subagents/context.md 13 KB
- references/subagents/generate.md 8.8 KB
- references/subagents/mr.md 5.7 KB
- references/subagents/plan.md 8.6 KB
- references/subagents/validate.md 6.9 KB
- scripts/qa-append-event.sh 1.8 KB runs code
- scripts/qa-assemble-meta.sh 4.1 KB runs code
- scripts/qa-e2e-smoke-test.sh 1.8 KB runs code
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.
- 2mo ago First seen · 315 lines · 181 tokens per session scan A 4f1243eb46cb
qa-e2e-generator is a skill published in the GitHub repository Jarroslav/agentic-os (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 181 tokens to every session and 3,917 once invoked, about $0.0007 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-08-31.
Other skills, from other repositories
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…
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.
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.
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.