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-chrome)<a href="https://agentmods.dev/commands/skyfox675/agents-skills/gh-issue-use-chrome"><img src="https://agentmods.dev/badge/commands/skyfox675/agents-skills/gh-issue-use-chrome/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-chrome"><img src="https://agentmods.dev/badge/commands/skyfox675/agents-skills/gh-issue-use-chrome.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.00374 |
| Opus 5 | $0.00029 | $0.00187 |
| Sonnet 5 | $0.00012 | $0.00075 |
| Haiku 4.5 | $0.00006 | $0.00037 |
Grade A, and why
gh-issue-use-chrome 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.
This is a copy
88% identical to gh-issue-use-aws-chrome — 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
/gh-issue-use-chrome — file a groomed GitHub issue, browser repro pinned to Chrome
Same as /gh-issue-use-browser, except the browser deep-dive uses the Chrome (claude-in-chrome) MCP specifically — best when the repro needs your real signed-in Chrome session (your cookies, your data). Run the browser-diagnosis skill on the Chrome MCP; if it is not connected, stop and say so, or use /gh-issue-use-browser to auto-pick another engine. Everything else — argument parsing, the filing flow, the ground rules, and the evidence captured — follows /gh-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.
- 10d ago First seen · 10 lines · 58 tokens per session scan A defc3a962864
gh-issue-use-chrome is a command published in the GitHub repository skyfox675/agents-skills (10 stars, last pushed 9d ago), licensed MIT. It adds 58 tokens to every session and 374 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to gh-issue-use-aws-chrome, differing in 8 lines, and is treated as a copy.
Other commands, from other repositories
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
can-i-use
Check browser support for web platform features against the project's browser targets.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.
verify-pr
Verify a PR's frontend changes through browser automation.
capture_full_page
Capture a full-page (entire scrollable page, beyond the viewport) or single-element screenshot through the Chrome debugger and save it under screenshots/. Unlike takescreenshot (viewport only, no debugger), this uses CDP to render the whole page or a specific element.
watch
Open a YouTube URL in your browser so the watcher plugin can auto play/pause it.