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.
git clone --depth 1 https://github.com/sigistry/marketplaceWrote 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/commands/sigistry/marketplace/generate-e2e-tests)<a href="https://agentmods.dev/commands/sigistry/marketplace/generate-e2e-tests"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/generate-e2e-tests/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/commands/sigistry/marketplace/generate-e2e-tests"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/generate-e2e-tests.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.00012 | $0.04022 |
| Opus 5 | $0.00006 | $0.02011 |
| Sonnet 5 | $0.00002 | $0.00804 |
| Haiku 4.5 | $0.00001 | $0.00402 |
Grade A, and why
generate-e2e-tests 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 — 554 lines — stays where its author put it; the contents beside it link to each section on GitHub.
End-to-End Test Generation Command
You are tasked with generating comprehensive end-to-end (E2E) tests for complete user workflows. These tests should simulate real user interactions and verify that the entire system works correctly from start to finish.
Step 1: Identify the Workflow
If the user provided a workflow name or feature:
- Understand the complete user journey
- Identify all steps in the workflow
- Map out the UI interactions, API calls, and data changes
If no specific workflow is provided:
- Ask the user which workflow or feature they want to test
- Suggest critical workflows: authentication, checkout, user registration, data submission, etc.
- Provide examples from the codebase if identifiable
Common workflows to consider:
- User registration and onboarding
- Login and authentication
- Shopping cart and checkout
- Content creation and publishing
- Search and filtering
- Form submission
- Multi-step wizards
- CRUD operations (Create, Read, Update, Delete)
Step 2: Detect E2E Testing Framework
Identify the E2E testing framework from the project:
JavaScript/TypeScript
- Playwright: Modern, cross-browser testing (check for @playwright/test)
- Cypress: Developer-friendly E2E framework (check for cypress)
- Selenium WebDriver: Classic browser automation
- Puppeteer: Chrome-specific automation
- TestCafe: No WebDriver browser testing
Python
- Playwright for Python: Cross-browser testing
- Selenium: Standard browser automation
- Behave: BDD-style testing
Java
- Selenium WebDriver: Browser automation
- Selenide: Simplified Selenium wrapper
Check project files:
package.json,requirements.txt,pom.xml,build.gradle- Existing test directories and test files
- Default to Playwright if not specified (modern standard)
Step 3: Map the Complete Workflow
For the identified workflow, document:
User Journey Steps
- Starting Point: Where does the user begin?
- Actions: What does the user do at each step?
- Navigation: How do they move between pages/screens?
- Inputs: What data do they enter?
- Validations: What feedback do they receive?
- Completion: What is the success state?
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 · 554 lines · 12 tokens per session scan A c3f67d9f5484
generate-e2e-tests is a command published in the GitHub repository sigistry/marketplace (3 stars, last pushed 4d ago), licensed MIT. It adds 12 tokens to every session and 4,022 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 commands, from other repositories
cloudflare-durable-objects:setup
Interactive Durable Objects project initialization. Scaffolds new DO project with proper bindings, migrations, and boilerplate code.
cloudflare-workers:test-setup
Interactive Vitest setup wizard for Cloudflare Workers testing. Configures @cloudflare/vitest-pool-workers, mocks bindings, and creates example tests.
test
Send synthetic webhook events to your local integration — valid, forged and replayed — and verify the handler responds correctly. Works for every provider in the catalog, not just the one with a CLI.
record
Record a browser walkthrough of a URL using Antigravity (agy). Generates .webm video, screenshots, and a report. Auto-converts to MP4 if ffmpeg is available.
validate
Mechanically validate the sonu plugin repo before a PR — manifest sync, YAML frontmatter, shell-fence syntax, named-source and AI-attribution scans, cross-reference integrity, skill reachability. Only meaningful inside the claude-plugins repo; in any other repo, say so and stop.
stark-quality-gate
Use this command when a web UI should be maintained, released, compared across runs, or used as public proof. It turns visual QA into a repeatable local/CI gate instead of a one-off screenshot check.