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-cloud-cligit 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-cloud-cli)<a href="https://agentmods.dev/skills/cypress-io/ai-toolkit/cypress-cloud-cli"><img src="https://agentmods.dev/badge/skills/cypress-io/ai-toolkit/cypress-cloud-cli/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-cloud-cli"><img src="https://agentmods.dev/badge/skills/cypress-io/ai-toolkit/cypress-cloud-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
- Socket pass
- Snyk warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 40 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- low Excessive Agency · line 107 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00079 | $0.01607 |
| Opus 5.5 | $0.00032 | $0.00643 |
| Sonnet 5.5 | $0.00016 | $0.00321 |
| Haiku 4.5 | $0.00008 | $0.00161 |
Grade A, and why
cypress-cloud-cli 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 25d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cypress Cloud CLI
Use cy-cloud directly to investigate Cypress Cloud. Execute the commands, inspect their JSON, and
report conclusions supported by the returned data. Do not send the user to the Cloud UI when the CLI
can answer the question.
Start safely
The published binary requires Node.js 22.21.0 or newer.
Run these checks only on first use, when the environment is unknown, or after an installation or
authentication error. If cy-cloud already worked in this session, invoke the investigation command
directly instead of spending another turn rechecking the setup.
node --version
cy-cloud status
cy-cloud --help
Assume cy-cloud is already installed and available on PATH. Run it from the user's current
workspace; do not locate, clone, build, or depend on the cloud-cli source repository. If the command
is unavailable, stop and report the missing prerequisite. The user can install it with:
npm install -g @cypress/cloud
If unauthenticated, ask the user to choose an authentication method:
cy-cloud login # interactive OAuth
cy-cloud login --token "$PAT" # persist a Personal Access Token
For CI or an existing environment, CYPRESS_CLOUD_TOKEN takes precedence over stored credentials
and writes no credential file.
Never print, echo, read back, or commit tokens. Never inspect
~/.config/cy-cloud/auth.json or cypress.env.json; use cy-cloud status.
The organization must have the Cypress Cloud CLI integration enabled. A response saying it is not enabled requires action from an organization administrator; it cannot be fixed with another CLI command.
Discover instead of guessing
Every command supports:
cy-cloud --help
cy-cloud <command> --help
cy-cloud <command> --schema
Treat cy-cloud --help as authoritative for available commands, per-command --help as
authoritative for arguments, and --schema as the intended response contract. Use them before
constructing a query when a command, flag, or field is uncertain. Do not memorize a command
inventory from this skill; the installed CLI may be newer or older than these instructions.
Validate the actual response too: run get can return a fractional duration, and
replay info.failedAt can be a fractional epoch even when the schema declares an integer. Treat
those values as numbers and report the schema mismatch if it matters; do not discard or round the
data.
What ships with it
4 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.
- 25d ago Changed · +3 lines 5638900b520d
- 1mo ago First seen · 148 lines · 79 tokens per session scan A 5b4b801513f9
cypress-cloud-cli is a skill published in the GitHub repository cypress-io/ai-toolkit (47 stars, last pushed today), licensed MIT. It adds 79 tokens to every session and 1,607 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-08-30.
Other skills, from other repositories
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…
ui-test-selector-review
A review guide for UI automation selectors, the rules tests use to find buttons, fields, and other interface elements.
ui-test-strategy
A guide for defining a UI test strategy across user journeys, interface states, platforms, and risks.
ui-test-wait-strategy-review
A review guide for asynchronous waits in UI tests, including polling conditions and timeout evidence.
visual-regression-testing
A guide for planning visual regression tests, which compare a current interface with an earlier approved image to find unintended visual changes.
ui-test-cypress
Use this skill when you need to design Cypress e2e and component testing plans with commands, fixtures, network stubbing, and CI reporting; triggers include Cypress UI testing, UI automation testing, and ui-test-cypress.