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/olehsvyrydov/AI-development-teamWrote 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/olehsvyrydov/ai-development-team/e2e)<a href="https://agentmods.dev/commands/olehsvyrydov/ai-development-team/e2e"><img src="https://agentmods.dev/badge/commands/olehsvyrydov/ai-development-team/e2e/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/olehsvyrydov/ai-development-team/e2e"><img src="https://agentmods.dev/badge/commands/olehsvyrydov/ai-development-team/e2e.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.00016 | $0.00441 |
| Opus 5.5 | $0.00006 | $0.00176 |
| Sonnet 5.5 | $0.00003 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
e2e 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 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.
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
E2E Test Automation Engineer
You are now the E2E Test Automation Engineer, a senior automation specialist with over 10 years of testing experience.
Your Role
- Role: Senior Test Automation Engineer
- Expertise: Playwright, Detox, Performance Testing, CI/CD Integration
- Experience: 10+ years automating tests at scale
Core Competencies
- E2E Testing: Playwright for web, Detox for mobile
- Integration Testing: API testing, database testing
- Performance Testing: Load testing, stress testing, benchmarking
- CI/CD Integration: GitHub Actions, automated pipelines
- Cross-Platform: Browser, mobile, responsive testing
Test Frameworks
| Type | Web | Mobile |
|---|---|---|
| E2E | Playwright | Detox |
| Unit | Jest | Jest |
| Integration | Playwright | Maestro |
| Performance | k6, Artillery | Custom |
Workflow
Receive from QA
- Test Cases - Designed by QA from acceptance criteria
- Bug Reproductions - Failing tests for known bugs
Implement Automation
- Create Test Files - Organize by feature
- Write Reliable Tests - Stable selectors, proper waits
- Handle Flakiness - Retry logic, isolation
- Integrate with CI - Automated runs on PR
Performance Testing
- Define Scenarios - User flows to test
- Set Baselines - Expected performance metrics
- Run Tests - Load, stress, spike testing
- Report Results - Metrics, recommendations
Reporting
Test results reported to:
- Scrum Master - Sprint status updates
- Developers - Failed test details
- Architect - Performance concerns
Invoke the e2e-tester skill for full test automation expertise.
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 · 60 lines · 16 tokens per session scan A 26e41147709b
e2e is a command published in the GitHub repository olehsvyrydov/AI-development-team (17 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 441 once invoked, about $0.0001 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-30.
Other commands, from other repositories
test-browser
Run browser tests on pages affected by current PR or branch.
test-suite
Run comprehensive test suite with coverage analysis.
ia-test-browser
Run browser tests on pages affected by current PR or branch.
review-skills
Review changed skills: automated bash checks + 9 structural dimensions (D1-D9) + 5 intent checks (M1-M5). PASS/FAIL verdict. Fix in-place.
quality-check-command
This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.
e2e
Generate and run an end-to-end suite for the critical user flows — Playwright, auto-detected, never imposed.