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.
git clone --depth 1 https://github.com/skyfox675/agents-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/commands/skyfox675/agents-skills/jira-issue-use-cypress)<a href="https://agentmods.dev/commands/skyfox675/agents-skills/jira-issue-use-cypress"><img src="https://agentmods.dev/badge/commands/skyfox675/agents-skills/jira-issue-use-cypress/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/commands/skyfox675/agents-skills/jira-issue-use-cypress"><img src="https://agentmods.dev/badge/commands/skyfox675/agents-skills/jira-issue-use-cypress.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.00049 | $0.00406 |
| Opus 5 | $0.00024 | $0.00203 |
| Sonnet 5 | $0.00010 | $0.00081 |
| Haiku 4.5 | $0.00005 | $0.00041 |
Grade A, and why
jira-issue-use-cypress 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
/jira-issue-use-cypress — file a groomed Jira issue, browser repro pinned to Cypress
Same as /jira-issue-use-browser, except the browser deep-dive uses the Cypress MCP specifically — for projects standardized on Cypress. Run the browser-diagnosis skill on the Cypress MCP; if it is not connected, stop and say so, or use /jira-issue-use-browser to auto-pick another engine. The Cypress MCP tools are pre-approved above — add the server to your MCP config under the key cypress (npx cypress-mcp --project ., needs Cypress ≥ 12 and npx playwright install chromium); capture network with a cypress_evaluate fetch shim per the browser-diagnosis skill. Everything else — argument parsing, the filing flow, the ground rules, and the evidence captured — follows /jira-issue-use-browser.
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 First seen · 10 lines · 49 tokens per session scan A e251fcc6f819
jira-issue-use-cypress is a command published in the GitHub repository skyfox675/agents-skills (10 stars, last pushed 10d ago), licensed MIT. It adds 49 tokens to every session and 406 once invoked, about $0.0002 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-31.
Other commands, from other repositories
browser
Debug and fix browser issues by inspecting, diagnosing, and resolving visual or technical problems.
interactive-dev
Start a persistent interactive development session with natural language browser control, auto-error monitoring, and full dev tool access.
run_slash_command
Execute SN Utils slash commands on a ServiceNow tab. Particularly useful for debugging forms with /tn (show technical names).
iterate-browser
Iterate on the current task using debug instrumentation and browser tools. Do not stop or ask the user to test manually.
browser-debug
A command recipe for starting Yandex Browser with remote debugging enabled through the Chrome DevTools Protocol, a browser control and inspection interface. It also checks whether the debugging connection is available.
chrome-browser
Browser automation with two integrations - Chrome DevTools MCP (always available, performance tracing) and Claude-in-Chrome extension (authenticated sessions, GIF recording). Use DevTools for testing/debugging, Claude-in-Chrome for authenticated workflows.