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 agentmods add skills/redhatinsights/nxtcm-components/e2e-test-implementationnpx skills add RedHatInsights/nxtcm-components --skill e2e-test-implementationgit clone --depth 1 https://github.com/RedHatInsights/nxtcm-componentsWrote 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/redhatinsights/nxtcm-components/e2e-test-implementation)<a href="https://agentmods.dev/skills/redhatinsights/nxtcm-components/e2e-test-implementation"><img src="https://agentmods.dev/badge/skills/redhatinsights/nxtcm-components/e2e-test-implementation.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 | $0.00026 | $0.04056 |
| Opus 5 | $0.00013 | $0.02028 |
| Sonnet 5 | $0.00005 | $0.00811 |
| Haiku 4.5 | $0.00003 | $0.00406 |
Grade A, and why
e2e-test-implementation 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 4d 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 — 425 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Test Implementation Guide
Systematic guide for implementing E2E tests identified in the test gap analysis (packages/nxtcm-rosa-hcp-wizard/docs/testing/E2E-TEST-GAPS.md), with reusable patterns for complex validation scenarios.
When to Use This Skill
Invoke this skill when:
- Implementing E2E tests from
packages/nxtcm-rosa-hcp-wizard/docs/testing/E2E-TEST-GAPS.md - Adding tests for cross-field validation (CIDR overlaps, VPC/subnet dependencies)
- Testing state management and navigation workflows
- Writing helper functions for wizard test automation
- Prioritizing test implementation from the backlog
Test Implementation Priority
From packages/nxtcm-rosa-hcp-wizard/docs/testing/E2E-TEST-GAPS.md, tests are classified:
HIGH Priority ⚠️
Add these first - critical user workflows and complex business logic:
- VPC change resets subnet selection
- CIDR overlap validations (Machine/Service/Pod mutual disjoint)
- Machine CIDR subnet containment
- Service/Pod CIDR subnet non-overlap
- Edit from Review workflow
- Back button state preservation
- Machine CIDR prefix boundaries (multi-AZ vs single-AZ)
MEDIUM Priority
Important functionality, lower risk: 8. Review page comprehensive field verification 9. Validation blocks navigation 10. Service CIDR prefix boundaries 11. Valid input acceptance tests (positive cases)
LOW Priority
Nice-to-have coverage: 12. Rapid selection change race conditions 13. Default CIDR value application 14. Accessibility (keyboard navigation)
Test Implementation Patterns
Pattern 1: Cross-Field Validation (CIDR Overlap)
Use case: Testing Machine/Service/Pod CIDRs must be mutually disjoint
test('CIDR fields - must be mutually disjoint', async ({ page }) => {
await openCidrFields(page);
// Set Machine CIDR
await page.getByRole('textbox', { name: 'Machine CIDR' }).fill('10.0.0.0/16');
await page.getByRole('textbox', { name: 'Machine CIDR' }).press('Tab');
// Service CIDR overlaps Machine
const serviceCidr = page.getByRole('textbox', { name: 'Service CIDR' });
await serviceCidr.fill('10.0.0.0/16');
await serviceCidr.press('Tab');
await expect(page.getByText(/overlaps.*Machine CIDR/i)).toBeVisible();
// Fix Service CIDR
await serviceCidr.fill('172.30.0.0/16');
await serviceCidr.press('Tab');
await expect(page.getByText(/overlaps/i)).not.toBeVisible();
});
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.
- 4d ago First seen · 425 lines · 26 tokens per session scan A 2c6995f324c1
e2e-test-implementation is a skill published in the GitHub repository RedHatInsights/nxtcm-components (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 4,056 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-08-31.
Other skills, from other repositories
Playwright Test Builder
Generates robust Playwright end-to-end tests for web pages and user flows.
browser-automation
Browser automation with Playwright — testing, scraping, monitoring, form submission, screenshot capture, and multi-page interaction flows. Covers setup, navigation, element interaction, assertions, and cleanup. Primary keyword clusters: Playwright browser automation, end-to-end testing with Playwright, web scraping…
playwright-test
Run end-to-end browser tests using the Playwright Test CLI. Create test configs, write spec files with expect assertions, execute tests with npx playwright test, and analyze results. Pre-installed with Chromium in the computer image — no setup needed. Use for E2E testing, regression testing, smoke tests, visual…
Playwright Browser Automation
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions…
e2e-testing-patterns
Build reliable, fast E2E test suites with Playwright and Cypress. Critical user journey coverage, flaky test elimination, CI/CD integration.
flow-tester
End-to-end user journey tester using Playwright. Tests multi-step flows (signup, checkout, CRUD) with screenshots at each step. Auto-generates flows from URLs or text descriptions. Use after integration work to verify complete user journeys work.