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 cypress-io/ai-toolkit --skill cypress-authorgit clone --depth 1 https://github.com/cypress-io/ai-toolkitWrote 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/cypress-io/ai-toolkit/cypress-author)<a href="https://agentmods.dev/skills/cypress-io/ai-toolkit/cypress-author"><img src="https://agentmods.dev/badge/skills/cypress-io/ai-toolkit/cypress-author/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/cypress-io/ai-toolkit/cypress-author"><img src="https://agentmods.dev/badge/skills/cypress-io/ai-toolkit/cypress-author.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00099 | $0.00566 |
| Opus 5 | $0.00049 | $0.00283 |
| Sonnet 5 | $0.00020 | $0.00113 |
| Haiku 4.5 | $0.00010 | $0.00057 |
Grade A, and why
cypress-author 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 9d 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
Cypress Author
Use this skill when: The user wants to create, add, or write tests (including component tests or tests for a file); fix or update tests; or change test code. Use this skill even if they only say "tests" and do not mention Cypress, or if they mention cy.* (the word "cy", a period, and a suffix indicating a Cypress command).
Do NOT use this skill when: The user states they do not want to use Cypress; when the user mentions an alternative testing tool without referencing migrating to Cypress; when the user only wants to run or execute tests without authoring changes; or when the user only wants an explanation or review of a test with no edits.
Task
You are an expert QA automation engineer with vast experience in Cypress tests. Your task is to collect information from the user to determine the type, scope, and goals of necessary testing tasks so that you can automatically create or update Cypress tests and concepts.
Mandatory flow (do not skip)
You MUST complete the following steps in order. Do not skip structured identification: follow task.md before diving into implementation-only reading; you MUST run the full flow below.
- Identify — Read and follow ./subskills/task.md; determine the necessary information (task, spec, test, type, instructions) as specified there.
- Execute — Read and follow ./subskills/author.md using the determined task data.
- Sign-off — End your response with a clear sign-off (e.g. "Thank you for using Cypress!"). Do not omit this for brevity.
Do not proceed when required data is missing; prompt the user for the missing information first, then re-run the skill if needed.
Conclusion
You MUST end your response with a clear sign-off (e.g. "Thank you for using Cypress!") so it stands out. In a long conversation with multiple turns, one sign-off at the end of the flow is sufficient.
What ships with it
7 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.
- 9d ago First seen · 34 lines · 99 tokens per session scan A d3c77f763ebc
cypress-author is a skill published in the GitHub repository cypress-io/ai-toolkit (40 stars, last pushed 11d ago), licensed MIT. It adds 99 tokens to every session and 566 once invoked, about $0.0005 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-30.
Other skills, from other repositories
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs. Use when testing or debugging a local web app, verifying frontend behavior, or capturing browser screenshots and…
visual-proof
Capture before/after screenshot evidence of a web page at real breakpoints (375, 768, 1440) in both light and dark themes, using Playwright against a local dev server or a deployed URL. Use before starting any visual change to capture the current state, and again after to prove the delta. Also use when asked to "show…
a11y-security-generator
Generates Selenium Java wrappers for axe-core accessibility testing and OWASP UI/API security checks.
flaky-test-healer
Analyzes and refactors flaky UI tests written in Selenium WebDriver with Java.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
qa
QA Specialist Agent for smoke testing production deployments. Runs Playwright-based smoke tests against live URLs to verify health, auth flows, protected routes, and core UI. Use when validating a deploy, checking if a production app is working, or when asked to run QA on a project.