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 parisgroup-ai/imersao-ia-setup --skill e2e-analyzegit clone --depth 1 https://github.com/parisgroup-ai/imersao-ia-setupWrote 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/parisgroup-ai/imersao-ia-setup/e2e-analyze)<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/e2e-analyze"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/e2e-analyze/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/parisgroup-ai/imersao-ia-setup/e2e-analyze"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/e2e-analyze.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.00046 | $0.01236 |
| Opus 5 | $0.00023 | $0.00618 |
| Sonnet 5 | $0.00009 | $0.00247 |
| Haiku 4.5 | $0.00005 | $0.00124 |
Grade A, and why
e2e-analyze 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 11d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
e2e-analyze - Failure Analysis
Analyze E2E failures with rich context: timeline, code correlation, and history.
Usage
/e2e-analyze # Analyze last run (from e2e-run-result.yaml)
/e2e-analyze <test> # Analyze specific test
Analysis Steps
Step 1: Load Last Run
cat apps/web/e2e-run-result.yaml
Step 2: For Each Failure, Build Timeline
Read the error-context.md file and reconstruct:
failure_timeline:
test: "creator-detail.spec.ts:29"
title: "should display creators list page"
steps:
- ts: "00:00.000"
action: "goto('/admin/creators')"
status: "ok"
- ts: "00:00.850"
action: "waitForLoadState('networkidle')"
status: "ok"
- ts: "00:01.200"
action: "locator('h1').filter({hasText: /criadores/})"
status: "timeout"
error: "Timeout 5000ms exceeded"
page_state:
url: "/admin/creators"
status_code: 404
screenshot: "test-results/.../test-failed-1.png"
Step 3: Code Correlation
For each failure, find related code:
code_correlation:
expected_route: "/admin/creators"
search_results:
- query: "glob: apps/web/src/app/**/admin/creators/**/page.tsx"
found: false
- query: "glob: apps/web/src/app/**/admin/**/creators/**/page.tsx"
found: true
path: "apps/web/src/app/(app)/admin/moderation/creators/page.tsx"
suggestion:
action: "test-update"
description: "Route /admin/creators doesn't exist. Use /admin/moderation/creators instead."
confidence: 0.95
Step 4: History Lookup
Check .e2e-history/failures.jsonl:
grep "creator-detail.spec.ts:29" .e2e-history/failures.jsonl | tail -5
grep "creator-detail.spec.ts:29" .e2e-history/resolutions.jsonl | tail -1
history:
previous_failures: 2
last_failure: "2026-01-15T10:30:00Z"
last_resolution:
date: "2026-01-15T11:00:00Z"
type: "test-update"
description: "Changed route from /admin/creators to /admin/moderation/creators"
pattern_detected: "Recurring route mismatch - may indicate unstable route structure"
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.
- 11d ago First seen · 169 lines · 46 tokens per session scan A 0335feaefa75
e2e-analyze is a skill published in the GitHub repository parisgroup-ai/imersao-ia-setup (1 stars, last pushed 29d ago), licensed MIT. It adds 46 tokens to every session and 1,236 once invoked, about $0.0002 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
e2e-testing
End-to-end testing for Falcon Foundry apps using Playwright and @crowdstrike/foundry-playwright. TRIGGER when user asks to "add e2e tests", "add playwright tests", "write end-to-end tests", "test my app", or mentions "e2e", "playwright", or "end-to-end" in the context of testing a Foundry app. DO NOT TRIGGER during…
browser-validator
Automatically validate implementations in real browsers after code is written or when user says "test this", "test what you built in the browser", "check it in a real browser", or "validate at the breakpoints". Uses Chrome DevTools MCP to test responsive breakpoints (320px, 768px, 1024px), check accessibility…
test-scaffolding
Automatically generate test scaffolding when user writes new code without tests or mentions needing tests. Supports unit, integration, e2e, and data tests for PHP and JavaScript. Invoke when user mentions "tests", "testing", "coverage", "write tests", or shows new untested code.
feature-acceptance
A browser-based acceptance testing process that compares an online implementation with a product requirements document and, when available, an HTML prototype. It records what is complete, partial, missing, or inconsistent, with screenshots and prioritized blockers.
Test Engineer
Creates or completes a medium-coverage test suite: unit, component, and critical e2e flows.
test-native-extension
Validate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCTEXPORTMETHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg…