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 RadOrigin-LLC/RAD-Claude-Skills --skill chrome-ext-troubleshootinggit clone --depth 1 https://github.com/RadOrigin-LLC/RAD-Claude-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/skills/radorigin-llc/rad-claude-skills/chrome-ext-troubleshooting)<a href="https://agentmods.dev/skills/radorigin-llc/rad-claude-skills/chrome-ext-troubleshooting"><img src="https://agentmods.dev/badge/skills/radorigin-llc/rad-claude-skills/chrome-ext-troubleshooting/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/radorigin-llc/rad-claude-skills/chrome-ext-troubleshooting"><img src="https://agentmods.dev/badge/skills/radorigin-llc/rad-claude-skills/chrome-ext-troubleshooting.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.00110 | $0.01172 |
| Opus 5 | $0.00055 | $0.00586 |
| Sonnet 5 | $0.00022 | $0.00234 |
| Haiku 4.5 | $0.00011 | $0.00117 |
Grade C, and why
chrome-ext-troubleshooting scanned grade C with 1 finding 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
grep -r "new Function(" .output/chrome-mv3/ ``` **Fix:** Replace the library, isolate in a sandbox page, or find an alternative. ### Accidental Secrets in Source ZIP Firefox requires a sources `.zip` that can rebuild the How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chrome Extension Troubleshooting
Common problems fall into three categories: build/packaging issues, runtime bugs, and Chrome Web Store rejections. Most have straightforward diagnoses once the pattern is recognized.
Build-Time Mistakes
Case-Sensitive File Paths
Windows is case-insensitive; CWS reviewer runs on Linux (case-sensitive). Background.js works locally but fails on submission (Yellow Magnesium rejection).
Fix: Verify all file paths match exactly, including capitalization. Test on a case-sensitive filesystem or review the packed .zip contents.
Missing web_accessible_resources
Content scripts cannot load extension assets (images, fonts, CSS) without declaring them:
{
"web_accessible_resources": [{
"resources": ["images/*", "fonts/*"],
"matches": ["<all_urls>"]
}]
}
Indirect eval() from npm Packages
Third-party libraries may internally use eval(), violating MV3 CSP. Audit dependencies:
# Search for eval in bundled output
grep -r "eval(" .output/chrome-mv3/
grep -r "new Function(" .output/chrome-mv3/
Fix: Replace the library, isolate in a sandbox page, or find an alternative.
Accidental Secrets in Source ZIP
Firefox requires a sources .zip that can rebuild the extension. .env files or secrets may leak:
Fix: Add .env*, *.pem, and credentials to .gitignore and verify they're excluded from the ZIP.
Runtime Debugging
| Symptom | Likely Cause | Fix |
|---|---|---|
| Event not firing after restart | Listener inside async function | Move to top level, register synchronously |
| State lost between events | Global variables in service worker | Use chrome.storage |
| Timer not executing | setTimeout in service worker |
Replace with chrome.alarms |
Message response is null |
Missing return true in async listener |
Add return true |
| Content script not injecting | Missing matches or permissions |
Check manifest and host permissions |
| Fetch failing in service worker | Using XMLHttpRequest |
Replace with fetch() |
| Storage writes silently failing | Sync quota exceeded | Check quotas, batch writes |
| Popup state disappears | Relying on React state only | Back with chrome.storage |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 121 lines · 110 tokens per session scan C a490502dacda
chrome-ext-troubleshooting is a skill published in the GitHub repository RadOrigin-LLC/RAD-Claude-Skills (5 stars, last pushed 24d ago), licensed Apache-2.0. It adds 110 tokens to every session and 1,172 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 1 finding (downloads and executes remote code). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
bug-reporting
Load this skill whenever you are filing, reviewing, or generating accessibility bug reports — whether from automated tool output, manual testing, user reports, or testing with disabled people. The purpose of this skill is to make accessibility findings easier to report accurately, connect them to real people and…
upstream-first
Load this skill before implementing a fix for a barrier that may originate in a shared component, design system, renderer, or external dependency rather than this project's own code. Decide whether the responsible fix is local, an existing installed capability, or an upstream contribution before writing a workaround.…
launchworthy
Production readiness audit that turns a demo into a real product. Built for apps shipped fast with AI coding tools (Lovable, Bolt, v0, Cursor, Claude Code). Auto-detects your stack and audits 5 domains (Frontend, Backend & Data, Auth & Security, Infrastructure, Operations), then produces a scored scorecard and a…
rudder-destination-debugging
Diagnoses why events are failing, dropping, or not arriving at a destination. Use when events are missing from a destination, seeing high error rates, getting auth failures, or events are stuck retrying.
rudder-instrumentation-debugging
Diagnoses and fixes validation errors, schema issues, and instrumentation problems. Use when debugging validation errors, schema issues, or instrumentation problems.
code-review
Perform comprehensive code reviews covering bugs, style, performance, security, and best practices. Use this skill when the user mentions: review my code, check this code, code review, find bugs, improve code, refactor suggestions, security audit, performance optimization, code quality, static analysis.