Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/djscheuf/agentic-dev-ecosystem-templatenpx agentmods add skills/djscheuf/agentic-dev-ecosystem-template/debug-e2e-workflowWrote 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/djscheuf/agentic-dev-ecosystem-template/debug-e2e-workflow)<a href="https://agentmods.dev/skills/djscheuf/agentic-dev-ecosystem-template/debug-e2e-workflow"><img src="https://agentmods.dev/badge/skills/djscheuf/agentic-dev-ecosystem-template/debug-e2e-workflow/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/djscheuf/agentic-dev-ecosystem-template/debug-e2e-workflow"><img src="https://agentmods.dev/badge/skills/djscheuf/agentic-dev-ecosystem-template/debug-e2e-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00049 | $0.02380 |
| Opus 5.5 | $0.00020 | $0.00952 |
| Sonnet 5.5 | $0.00010 | $0.00476 |
| Haiku 4.5 | $0.00005 | $0.00238 |
Grade A, and why
debug-e2e-workflow 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Test Debugging Workflow
Purpose
Systematically debug E2E test failures across multiple tests by reviewing evidence, forming hypotheses, applying TDD-style fixes, and verifying the result.
Overview
This workflow runs through four phases in order. The first three phases have detailed supporting documents in this skill directory; the main file provides the map and decision points.
┌─────────────────────────────────────────────────────────────────────┐
│ E2E DEBUGGING CYCLE (Two-Path) │
│ │
│ ┌──────────┐ ┌────────────────────────────────────────┐ │
│ │ REVIEW │───▶│ HYPOTHESIS │ │
│ │ │ │ │ │
│ │ Classify │ │ ┌──────────────┐ ┌──────────────┐ │ │
│ │ Each │ │ │ Setup │ │ Test Exec │ │ │
│ │ Test: │ │ │ Failures │ │ Failures │ │ │
│ │ │ │ │ (Infra/Env) │ │ (App/Test) │ │ │
│ │ • Setup │ │ └──────┬───────┘ └──────┬───────┘ │ │
│ │ Failure│ │ │ │ │ │
│ │ • Test │ │ Priority 0 Priority 1+ │ │
│ │ Exec │ │ (Fix FIRST) (Fix AFTER) │ │
│ │ Failure│ │ │ │ │ │
│ └──────────┘ └─────────┼──────────────────┼───────────┘ │
│ │ │ │
│ ▼ │ │
│ ┌──────────────────┐ │ │
│ │ FIX Setup Issues │ │ │
│ │ (see /reference/fix.md) │ │ │
│ └────────┬─────────┘ │ │
│ │ │ │
│ ▼ │ │
│ ┌──────────────────┐ │ │
│ │ RE-RUN TESTS │ │ │
│ │ (Get clean │ │ │
│ │ results) │ │ │
│ └────────┬─────────┘ │ │
│ │ │ │
│ └────────────────────┘ │
│ │ │
│ ▼ │
│ ┌──────────────────┐ │
│ │ FIX Test Issues │ │
│ │ (see /reference/fix.md) │ │
│ └────────┬─────────┘ │
│ │ │
│ ▼ │
│ ┌──────────────────┐ │
│ │ FINAL VERIFY │ │
│ │ & COMMIT │ │
│ └──────────────────┘ │
└─────────────────────────────────────────────────────────────────────┘
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 233 lines · 49 tokens per session scan A 86d412882dd2
debug-e2e-workflow is a skill published in the GitHub repository djscheuf/agentic-dev-ecosystem-template (12 stars, last pushed 20d ago), licensed MIT. It adds 49 tokens to every session and 2,380 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-30.
Other skills, from other repositories
reproduce-bug
Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
webapp-qa
Perform scoped exploratory QA of a web application, reproduce defects, collect screenshots and console evidence, and deliver a prioritized report.
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…
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…