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/gh-issue-use-aws-playwright)<a href="https://agentmods.dev/commands/skyfox675/agents-skills/gh-issue-use-aws-playwright"><img src="https://agentmods.dev/badge/commands/skyfox675/agents-skills/gh-issue-use-aws-playwright/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/gh-issue-use-aws-playwright"><img src="https://agentmods.dev/badge/commands/skyfox675/agents-skills/gh-issue-use-aws-playwright.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.00059 | $0.00395 |
| Opus 5 | $0.00030 | $0.00198 |
| Sonnet 5 | $0.00012 | $0.00079 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade A, and why
gh-issue-use-aws-playwright 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 10d 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
/gh-issue-use-aws-playwright — correlated full-stack dive, browser pinned to Playwright
Same as /gh-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 Playwright MCP specifically, a clean automated browser for a public page or one reachable with test credentials. Run the browser-diagnosis skill on Playwright; if it is not connected, use /gh-issue-use-aws-browser to auto-pick another engine. The AWS ground rules, the correlation method, the trace table, and everything else follow /gh-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.
- 10d ago First seen · 10 lines · 59 tokens per session scan A e353993654e9
gh-issue-use-aws-playwright is a command published in the GitHub repository skyfox675/agents-skills (10 stars, last pushed 9d ago), licensed MIT. It adds 59 tokens to every session and 395 once invoked, about $0.0003 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
splunk-observability-synthetics-setup
Render focused Splunk Observability Synthetic Monitoring plans and native-ops specs for browser, API, HTTP, SSL, and port tests.
e2e
Generate comprehensive E2E tests for user workflows using Playwright.
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.
scan
Scan AWS account for cost optimization.