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 jxoesneon/Ciel --skill e2e-and-visual-verificationgit clone --depth 1 https://github.com/jxoesneon/CielWrote 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/jxoesneon/ciel/e2e-and-visual-verification)<a href="https://agentmods.dev/skills/jxoesneon/ciel/e2e-and-visual-verification"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/e2e-and-visual-verification/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/jxoesneon/ciel/e2e-and-visual-verification"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/e2e-and-visual-verification.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.00025 | $0.00539 |
| Opus 5 | $0.00013 | $0.00269 |
| Sonnet 5 | $0.00005 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
e2e-and-visual-verification 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
CIEL ADAPTATION: E2E & Visual Verification (The Interface Layer)
This skill manages the correctness and quality of user interfaces. it prioritizes stable test patterns and intentional design choices over generic UI.
E2E Testing (Playwright)
- POM Mandate: Use Page Object Models for all tests to isolate selectors from logic.
- Stability: Prohibit
waitForTimeout(). Use auto-waiting locators orwaitForResponse(). - Flakiness Protocol: Quarantine flaky tests with
test.fixme(). Identify root causes via--repeat-each=10. - Artifacts: ALWAYS capture screenshots and traces on failure in CI.
Intentional Frontend Design
- Direction: Pick a visual direction (Minimal, Industrial, Editorial) and commit to it.
- Hierarchy: Use strong whitespace and asymmetrical overlaps to clarify focus.
- Motion: Use animation only to reveal hierarchy or reinforce action. One well-directed load sequence > many micro-interactions.
- Tokens: Use CSS variables for all colors, spacing, and typography. No random hex values.
Visual Regression
- Breakpoints: Verify layouts at Mobile (375px), Tablet (768px), and Desktop (1440px).
- Hard Gate: Flag layout shifts > 5px or overlapping elements in PR reviews.
Anti-Patterns
- Generic AI UI: Defaulting to purple-gradient-on-white card grids without a specific brand reason.
- Selector Fragility: Using brittle CSS selectors in E2E tests instead of
data-testid. - Amnesiac Cleanup: Creating E2E data (e.g., users) without a teardown or
RefreshDatabasestrategy.
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 · 51 lines · 25 tokens per session scan A 976f441b5626
e2e-and-visual-verification is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 25 tokens to every session and 539 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
playwright-uitest
Generate Playwright UI tests and visual smoke reports for delivery POC frontends.
browser-automation
Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, and anti-detection patterns. This skill covers Playwright (recommended) and Puppeteer, with patterns for testing, scraping…
browser-testing
A browser-based end-to-end testing workflow, where end-to-end testing means checking a complete user-facing feature through the browser, with test cases stored in Markdown files.
nobrainer-browser
Use when the owner says nb-browser or nobrainer-browser, asks to inspect or operate a rendered website, attach to an existing approved Chrome/Edge session, restart an approved non-default Chromium profile for loopback CDP, reproduce a browser flow, run Playwright tests, or record and analyze a Playwright trace. Prefer…
e2e-testing
End-to-end testing workflow with Playwright for browser automation, visual regression, cross-browser testing, and CI/CD integration.
playwright
Direct browser automation (navigate, click, type, screenshot, evaluate) using Playwright — no MCP server required.