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 eea/eea.agent.skills --skill volto-cypress-writergit clone --depth 1 https://github.com/eea/eea.agent.skillsWrote 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/eea/eea.agent.skills/volto-cypress-writer)<a href="https://agentmods.dev/skills/eea/eea.agent.skills/volto-cypress-writer"><img src="https://agentmods.dev/badge/skills/eea/eea.agent.skills/volto-cypress-writer/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/eea/eea.agent.skills/volto-cypress-writer"><img src="https://agentmods.dev/badge/skills/eea/eea.agent.skills/volto-cypress-writer.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.00063 | $0.01866 |
| Opus 5.5 | $0.00025 | $0.00746 |
| Sonnet 5.5 | $0.00013 | $0.00373 |
| Haiku 4.5 | $0.00006 | $0.00187 |
Grade A, and why
volto-cypress-writer 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 19d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Volto Cypress Writer
Use this skill when writing, updating, reviewing, or debugging Cypress tests for EEA Plone/Volto add-ons and projects.
Discover the project first
EEA Volto codebases come from more than one template generation, and their Cypress setup differs. Before editing, read:
cypress.config.js— thespecPattern,baseUrl, reporter, and setup eventsMakefile— runmake helpfor the real Cypress targetscypress/support/e2e.jsandcypress/support/commands.js— the helper layout- nearby specs — the existing naming and helper style
Put new specs where the project's specPattern points, not in a hardcoded
directory. Common layouts are cypress/e2e/**/*.cy.js (legacy add-ons) and
cypress/tests/**/*.cy.{js,jsx,ts,tsx} (Cookieplone projects/add-ons).
Put reusable feature helpers in cypress/support/<feature>.js unless the project
already uses a different convention. Keep global Cypress commands minimal;
prefer imported helpers for feature-specific flows.
UI-First Rule
New tests must set up state, navigate, edit, save, and assert through the browser UI.
- Do not add or call
cy.request()setup helpers for new tests unless the user explicitly asks for legacy/API-seeded style. - Existing REST helpers such as
autologin,createContent, andremoveContentmay be read for context, but do not copy them into new UI-first flows. - Use the UI for the behavior under test even when an older suite uses API shortcuts.
- If UI-only setup is impractical for a narrow reason, stop and explain the constraint before changing the approach.
Selectors
- Prefer stable
data-cyordata-testidselectors. - If stable selectors are missing and component edits are in scope, add explicit test selectors to the component instead of relying on DOM shape.
- Use role, label, placeholder, or visible text when they describe the user's intent.
- Avoid positional selectors like
:nth-child()and style-driven selectors like.ui.basic.icon.button.... - If Volto or Semantic UI markup forces a fragile selector, hide it behind a named helper such as
openBlockChooser()orsaveCurrentPage(). - Keep assertions user-visible where possible: URL, heading, block text, saved view output, modal state, toolbar state, validation message.
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.
- 19d ago First seen · 198 lines · 63 tokens per session scan A 66ccfa14a566
volto-cypress-writer is a skill published in the GitHub repository eea/eea.agent.skills (5 stars, last pushed 20d ago), licensed MIT. It adds 63 tokens to every session and 1,866 once invoked, about $0.0003 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-09-28.
Other skills, from other repositories
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
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.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
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.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
critique
Adversarial design critique of the current work — render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.