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 elevanaltd/HestAI-MCP --skill e2e-test-strategygit clone --depth 1 https://github.com/elevanaltd/HestAI-MCPWrote 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/elevanaltd/hestai-mcp/e2e-test-strategy)<a href="https://agentmods.dev/skills/elevanaltd/hestai-mcp/e2e-test-strategy"><img src="https://agentmods.dev/badge/skills/elevanaltd/hestai-mcp/e2e-test-strategy/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/elevanaltd/hestai-mcp/e2e-test-strategy"><img src="https://agentmods.dev/badge/skills/elevanaltd/hestai-mcp/e2e-test-strategy.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.00000 | $0.00613 |
| Opus 5 | $0.00000 | $0.00307 |
| Sonnet 5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
e2e-test-strategy 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 6d 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_STRATEGY=== META: TYPE::SKILL VERSION::"1.0.0" STATUS::ACTIVE PURPOSE::"End-to-end validation design, user journey mapping, and integration sign-off methodology"
§1::CORE AUTHORITY::ADVISORY[test_strategy_design⊕coverage_gaps⊕sign_off_evidence] SCOPE::e2e_test_design⊕execution_planning⊕integration_sign_off MISSION::"Design E2E validation that proves system behavior across component boundaries"
§2::PROTOCOL
TEST_DESIGN::[ 1::map_user_journeys<critical_paths⊕happy_paths⊕error_paths>, 2::identify_cross_component_scenarios<data_flows_spanning_services>, 3::define_assertion_points<input_boundary⊕transformation⊕output_boundary>, 4::establish_test_data_strategy<fixtures⊕factories⊕seed_data>, 5::determine_environment_requirements<infra⊕external_dependencies⊕mocks_vs_real> ]
TEST_BOUNDARY::[ E2E::full_user_journey<browser_or_CLI_to_database_and_back>, INTEGRATION::component_pair_contract<API_producer_consumer>, UNIT::isolated_logic<no_external_dependencies>, RULE::"E2E validates what integration and unit tests cannot — cross-cutting user outcomes" ]
EXECUTION_PROTOCOL::[ SEQUENCE::unit→integration→e2e<pyramid_enforcement>, ISOLATION::each_e2e_test_independent<no_shared_state>, STABILITY::retry_flaky_once<if_still_fails→fix_not_skip>, TIMING::e2e_runs_post_integration_gate<not_on_every_commit> ]
SIGN_OFF_EVIDENCE::[ REQUIRED::all_critical_journeys_exercised, REQUIRED::cross_component_data_flow_verified, REQUIRED::error_paths_tested<not_just_happy_paths>, REQUIRED::performance_within_baseline_thresholds, FORMAT::test_report_with_journey_coverage_matrix ]
§3::GOVERNANCE
NEVER::[ substitute_e2e_for_unit_tests<wrong_layer>, skip_error_path_testing, sign_off_without_cross_component_evidence, mock_everything_in_e2e<defeats_purpose> ]
ESCALATION::test_infrastructure_gaps→implementation-lead
§5::ANCHOR_KERNEL TARGET::e2e_validation_proving_cross_component_user_outcomes NEVER::[substitute_e2e_for_unit,skip_error_paths,sign_off_without_evidence,mock_everything_in_e2e] MUST::[map_user_journeys_first,define_cross_component_scenarios,enforce_test_pyramid,require_sign_off_evidence] GATE::"Do E2E tests prove the system works across component boundaries for real user journeys?"
===END===
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.
- 6d ago First seen · 63 lines · 0 tokens per session scan A 43dd8fc376e6
e2e-test-strategy is a skill published in the GitHub repository elevanaltd/HestAI-MCP (0 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 613 tokens. 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
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.
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.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…