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-fix-cyclegit 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-fix-cycle)<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/e2e-fix-cycle"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/e2e-fix-cycle/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-fix-cycle"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/e2e-fix-cycle.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.00057 | $0.01256 |
| Opus 5.5 | $0.00023 | $0.00502 |
| Sonnet 5.5 | $0.00011 | $0.00251 |
| Haiku 4.5 | $0.00006 | $0.00126 |
Grade A, and why
e2e-fix-cycle 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.
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-fix-cycle - Automated Test-Fix Loop
Orchestrates e2e-run → e2e-analyze → fix → repeat until all tests pass.
Usage
/e2e-fix-cycle <target> # Full cycle for target
/e2e-fix-cycle admin-tests # Fix all admin test failures
Configuration
limits:
max_iterations: 5
max_auto_fixes_per_batch: 10
require_approval:
- code-create # Creating new files
- schema-change # Database changes
- seed-update # Test data changes
auto_approve:
- test-update # Updating test code
- wait-strategy # Changing wait patterns
Cycle Flow
┌─────────────────────────────────────────────────────────────┐
│ ITERATION 1 │
├─────────────────────────────────────────────────────────────┤
│ 1. /e2e-run admin-tests │
│ → 7 failures │
│ │
│ 2. /e2e-analyze │
│ → 2 batches: wrong-route(2), timeout-403(5) │
│ │
│ 3. FIX BATCH 1: wrong-route (auto-approve) │
│ → Edit creator-detail.spec.ts │
│ → Replace /admin/creators with /admin/moderation/creators│
│ │
│ 4. VERIFY BATCH 1 │
│ /e2e-run -g "creator-detail" --project=admin-tests │
│ → 2 tests now pass │
│ │
│ 5. FIX BATCH 2: timeout-403 (auto-approve) │
│ → Edit permission-boundaries.spec.ts │
│ → Replace networkidle with domcontentloaded │
│ │
│ 6. VERIFY BATCH 2 │
│ /e2e-run -g "permission-boundaries" --project=admin-tests│
│ → 5 tests now pass │
│ │
│ 7. FULL VERIFICATION │
│ /e2e-run admin-tests │
│ → 212 passed, 0 failed ✅ │
│ │
│ 8. LOG RESOLUTIONS │
│ → Append to .e2e-history/resolutions.jsonl │
│ │
│ 9. COMMIT │
│ git commit -m "fix(e2e): resolve admin test failures" │
└─────────────────────────────────────────────────────────────┘
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 · 169 lines · 57 tokens per session scan A b2a718b811a2
e2e-fix-cycle is a skill published in the GitHub repository parisgroup-ai/imersao-ia-setup (1 stars, last pushed 20d ago), licensed MIT. It adds 57 tokens to every session and 1,256 once invoked, about $0.0002 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-31.
Other skills, from other repositories
debugging
Playwright test debugging conventions for the scaffold — reading failure messages, classifying failure modes (TimeoutError, ZodError, strict-mode violation, locator not found, network errors, schema drift), the playwright.config.ts capture defaults (trace on-first-retry, screenshot only-on-failure, video…
proof-e2e
Build E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests".
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…
test-runner
Use this skill when orchestrating agentic end-to-end tests. Resolves target + profile, dispatches the right driver(s) (playwright for web today, peekaboo for macOS (issue #381)), invokes the ux-evaluator agent (opus, read-only) against driver artifacts, reconciles findings with the open issue tracker via…
wicked-garden-qe-incident-to-scenario-synthesizer
Turns a production incident into a deterministic scenario file that reproduces it. Takes an incident-report markdown OR direct fields (stack trace, endpoint URL, HTTP method, request body), extracts the minimal reproducer, writes scenarios/ .md with linkedtoincident: frontmatter, emits wicked.qe.scenario.authored with…
runtime-verification
Verify code works at runtime through build verification (mandatory), LSP diagnostics, ad-hoc verification for projects without frameworks, E2E and smoke tests, and visual verification (screenshot-analyze-verify for UI changes). Skip whitelist strictly enforced (markdown-only, config-only, dependency-bump-only with…