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-aws-cypress)<a href="https://agentmods.dev/commands/skyfox675/agents-skills/jira-issue-use-aws-cypress"><img src="https://agentmods.dev/badge/commands/skyfox675/agents-skills/jira-issue-use-aws-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-aws-cypress"><img src="https://agentmods.dev/badge/commands/skyfox675/agents-skills/jira-issue-use-aws-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.00058 | $0.00478 |
| Opus 5 | $0.00029 | $0.00239 |
| Sonnet 5 | $0.00012 | $0.00096 |
| Haiku 4.5 | $0.00006 | $0.00048 |
Grade A, and why
jira-issue-use-aws-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.
This is a copy
89% identical to gh-issue-use-aws-cypress — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
/jira-issue-use-aws-cypress — correlated full-stack dive, browser pinned to Cypress
Same as /jira-issue-use-aws-browser — the correlated full-stack diagnosis (reproduce in the browser, capture the failing request, chase it through the cloud with read-only AWS calls until the fault layer is found) — except the browser phase uses the Cypress MCP specifically, for projects standardized on Cypress. Run the browser-diagnosis skill on Cypress; if it is not connected, use /jira-issue-use-aws-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. The AWS ground rules, the correlation method, the trace table, and everything else follow /jira-issue-use-aws-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 · 58 tokens per session scan A 9625719240eb
jira-issue-use-aws-cypress is a command published in the GitHub repository skyfox675/agents-skills (10 stars, last pushed 11d ago), licensed MIT. It adds 58 tokens to every session and 478 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to gh-issue-use-aws-cypress, differing in 8 lines, and is treated as a copy.
Other commands, from other repositories
System Status
Check overall system health and status.
investigate
Start a deep root-cause investigation on the AWS DevOps Agent and stream progress.
cloudflare-queues:troubleshoot
Quick troubleshooting for common Cloudflare Queues issues.
cloudflare-workers:debug
Interactive debugging workflow for Cloudflare Workers. Diagnoses deployment errors, runtime issues, and performance problems with step-by-step fixes.
cloudflare-workflows:debug
Interactive debugging for failing workflow instances. Use when user reports workflow errors, instances stuck, or deployment failures.
cluster-health-check
Perform comprehensive health check on HCP cluster and report issues.