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 mattmre/EVOKORE-MCP-PUBLIC --skill orch-e2egit clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLICWrote 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/mattmre/evokore-mcp-public/orch-e2e)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/orch-e2e"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/orch-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/skills/mattmre/evokore-mcp-public/orch-e2e"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/orch-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.00015 | $0.00731 |
| Opus 5 | $0.00008 | $0.00365 |
| Sonnet 5 | $0.00003 | $0.00146 |
| Haiku 4.5 | $0.00002 | $0.00073 |
Grade A, and why
orch-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 7d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestration E2E
Purpose
Generate or run end-to-end tests for critical flows. Identifies key user journeys, creates test scenarios, and captures execution evidence.
Invocation
orch-e2e [action] [flow]
Actions: generate, run, verify
Arguments
| Argument | Required | Description |
|---|---|---|
| action | No | generate, run, or verify (default: run) |
| flow | No | Specific flow to test |
| config | No | Test configuration override |
Workflow
1. Identify Critical Flows
- Map user journeys and business flows
- Prioritize by risk and frequency
- Define test boundaries
2. Create Test Scenarios
- Write scenario descriptions
- Define preconditions and postconditions
- Specify expected outcomes
3. Generate/Run Tests
- Create test files (if generating)
- Execute test suite
- Capture results
4. Capture Evidence
- Document test outcomes
- Screenshot/log critical steps (if applicable)
- Update task tracking
Critical Flow Identification
Prioritize flows by:
- Business impact: Revenue, user retention
- Frequency: Most common user paths
- Risk: Error-prone or recently changed
- Compliance: Regulatory requirements
Test Scenario Template
## Scenario: <name>
### Preconditions
- User state: <logged in/guest/admin>
- Data state: <required fixtures>
- System state: <services running>
### Steps
1. <action>
2. <action>
3. <action>
### Expected Outcome
- <assertion>
- <assertion>
### Postconditions
- <cleanup actions>
Flow Categories
| Category | Examples |
|---|---|
| Authentication | Login, logout, password reset |
| Core features | Main user workflows |
| Transactions | Payments, orders, submissions |
| Admin | User management, configuration |
| Integration | Third-party service interactions |
Outputs
| Output | Description |
|---|---|
| Test files | E2E test scripts (if generating) |
| Results | Test execution summary |
| Evidence | Screenshots, logs, reports |
| Task update | E2E status logged |
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.
- 7d ago First seen · 147 lines · 15 tokens per session scan A 11a16bd45f4d
orch-e2e is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 15 tokens to every session and 731 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 skills, from other repositories
init
Set up Playwright in a project. Use when user says "set up playwright", "add e2e tests", "configure playwright", "testing setup", "init playwright", or "add test infrastructure".
playwright-pro
Production-grade Playwright testing toolkit. Use when the user mentions Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test migration, CI/CD testing, or test suites. Generate tests, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55 templates…
browserstack
Run tests on BrowserStack. Use when user mentions "browserstack", "cross-browser", "cloud testing", "browser matrix", "test on safari", "test on firefox", or "browser compatibility".
generate
Generate Playwright tests. Use when user says "write tests", "generate tests", "add tests for", "test this component", "e2e test", "create test for", "test this page", or "test this feature".
migrate
Migrate from Cypress or Selenium to Playwright. Use when user mentions "cypress", "selenium", "migrate tests", "convert tests", "switch to playwright", "move from cypress", or "replace selenium".
fix
Fix failing or flaky Playwright tests. Use when user says "fix test", "flaky test", "test failing", "debug test", "test broken", "test passes sometimes", or "intermittent failure".