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 monkilabs/opencastle --skill cypress-testinggit clone --depth 1 https://github.com/monkilabs/opencastleWrote 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/monkilabs/opencastle/cypress-testing)<a href="https://agentmods.dev/skills/monkilabs/opencastle/cypress-testing"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/cypress-testing/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/monkilabs/opencastle/cypress-testing"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/cypress-testing.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.00040 | $0.00377 |
| Opus 5.5 | $0.00016 | $0.00151 |
| Sonnet 5.5 | $0.00008 | $0.00075 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
cypress-testing 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 11d 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 Testing
Project test config and breakpoints: .opencastle/stack/testing-config.md. Docs: https://docs.cypress.io
Layout
Specs cypress/e2e/ • fixtures cypress/fixtures/ • custom commands cypress/support/commands.ts • failure artifacts cypress/screenshots/ and cypress/videos/.
Gotchas
cy.session(key, setupFn)caches and restores auth state across specs — the cache key must include every credential that changes the session, or you will silently reuse the wrong user.- Give each spec unique
@aliasnames forcy.intercept()routes. Shared alias names cause cross-testcy.wait()collisions when specs run in parallel. - Prefer
cy.intercept()with fixed fixture payloads over seeding real data — it is the only reliable fix for network flake. - Selector priority:
data-testid→aria-*/role. Never auto-generated classes or deep CSS paths. - After
npm install --save-dev cypress, runnpx cypress verify— a corrupted binary cache fails later with confusing errors.
Commands
npx cypress open # interactive
npx cypress run # headless / CI, assert exit 0
npx cypress run --spec "cypress/e2e/auth/login.cy.ts" --headed # single-spec smoke check
On failure, re-run the failing spec alone and inspect the screenshot/video artifacts. In CI, upload those artifacts only on failure.
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.
- 11d ago Changed · -29 tokens per session 7a9efdd29b2b
- 12d ago First seen · 31 lines · 69 tokens per session scan A c1a2bc095b35
cypress-testing is a skill published in the GitHub repository monkilabs/opencastle (80 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 377 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-10-04.
Other skills, from other repositories
webapp-testing
Web application testing principles. E2E, Playwright, deep audit strategies.
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
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…
smoke-test
Run smoke tests against a deployed or local app based on your git diff. Each test uses Skyvern browser tools (navigate, act, validate, screenshot) with Chrome DevTools MCP as fallback. Posts screenshot evidence as PR comments.