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/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/plugins/radorigin-llc/rad-claude-skills/rad-chrome-extension)<a href="https://agentmods.dev/plugins/radorigin-llc/rad-claude-skills/rad-chrome-extension"><img src="https://agentmods.dev/badge/plugins/radorigin-llc/rad-claude-skills/rad-chrome-extension/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/plugins/radorigin-llc/rad-claude-skills/rad-chrome-extension"><img src="https://agentmods.dev/badge/plugins/radorigin-llc/rad-claude-skills/rad-chrome-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rad-chrome-extension 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 9d 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
{
"name": "rad-chrome-extension",
"version": "1.1.0",
"description": "MV3 Chrome extension development standards (WXT, React, TypeScript) with two pure-stdlib Python validators that catch what LLM eyeballing misses. Skills cover architecture, MV3 security (CSP, remote code ban, content script isolation), permission minimization and CWS compliance, typed messaging, storage selection, service worker lifecycle, React UI patterns, testing, and Chrome Web Store troubleshooting.\n\nThe chrome-ext-reviewer agent runs two validators before LLM judgment: `audit-manifest.py` (manifest.json audit for MV3 compliance, permission overreach, weak CSP, web_accessible_resources scoping, MV2 leftovers, CWS-rejection causes; auto-discovers WXT `.output/` build manifests) and `scan-mv3-violations.py` (greps source for CSP-banned `eval` / `new Function` / `setTimeout('string')`, remote `<script src=\"http\">` and dynamic imports of remote URLs, MV2-only `chrome.tabs.executeScript` / `chrome.browserAction` / `chrome.extension.getBackgroundPage`, blocking webRequest listeners, optional DOM-risk `innerHTML` / `document.write`). Both emit findings with severity and specific fix recommendations. Pure stdlib Python 3.8+.",
"author": {
"name": "RAD",
"url": "https://github.com/RadOrigin-LLC"
},
"license": "Apache-2.0",
"homepage": "https://github.com/RadOrigin-LLC/RAD-Claude-Skills/tree/main/plugins/rad-chrome-extension",
"repository": "https://github.com/RadOrigin-LLC/RAD-Claude-Skills",
"keywords": ["chrome-extension", "manifest-v3", "wxt", "react", "typescript", "service-worker", "content-script", "chrome-web-store", "browser-extension", "mv3"]
}
What it installs
The manifest is a name and a version. 9 skills, 1 agent travel with it, and installing the plugin installs all of them — 1,294 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill chrome-ext-best-practices A 118 tokens
- Skill chrome-ext-messaging A 106 tokens
- Skill chrome-ext-permissions A 98 tokens
- Skill chrome-ext-service-worker A 111 tokens
- Skill chrome-ext-storage A 106 tokens
- Skill chrome-ext-testing A 101 tokens
- Skill chrome-ext-ui-react A 114 tokens
- Skill chrome-ext-security A 110 tokens
- Skill chrome-ext-troubleshooting C 110 tokens
- Agent chrome-ext-reviewer B 320 tokens
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.
- 9d ago First seen · 14 lines scan A 33a387b571a6
rad-chrome-extension is a plugin published in the GitHub repository RadOrigin-LLC/RAD-Claude-Skills (5 stars, last pushed 23d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
claude-skills marketplace
Agent settings configuring schemaversion, skills.
socialforge
17 composable social-media growth skills + an orchestrator. Analyze competitors, nail your audience, generate hooks and scripts, repurpose one video into 30+, ride trends, boost engagement, and adapt across every platform. Works with Claude and any capable model.
wes-bos-sick-picks
Research-first workflow for building modern, accessible frontend UI components in the spirit of Wes Bos. Researches pitfalls and platform capabilities before planning, designs for WCAG accessibility with modern web standards, then verifies the approach against Wes Bos on X plus trusted sources (MDN, web.dev…
VibesOS
Vibes is for people who use Claude Code, but don't know how to code.
fuse-react
Expert React 19 with hooks, TanStack Router, Zustand, React Hook Form, Testing Library, shadcn/ui, and SOLID principles.
instui
Claude Code tooling for Instructure UI (InstUI) — starting with documentation lookup from instructure.design's plaintext docs.