Borrowing it
Nothing to install: this file belongs to jgkme/Add-Remote-Torrent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jgkme/Add-Remote-Torrent/master/.cursor/skills/chrome-extension-mv3-workflow/SKILL.mdgit clone --depth 1 https://github.com/jgkme/Add-Remote-TorrentWrote 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/jgkme/add-remote-torrent/chrome-extension-mv3-workflow)<a href="https://agentmods.dev/skills/jgkme/add-remote-torrent/chrome-extension-mv3-workflow"><img src="https://agentmods.dev/badge/skills/jgkme/add-remote-torrent/chrome-extension-mv3-workflow/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/jgkme/add-remote-torrent/chrome-extension-mv3-workflow"><img src="https://agentmods.dev/badge/skills/jgkme/add-remote-torrent/chrome-extension-mv3-workflow.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.00045 | $0.00267 |
| Opus 5 | $0.00023 | $0.00133 |
| Sonnet 5 | $0.00009 | $0.00053 |
| Haiku 4.5 | $0.00005 | $0.00027 |
Grade A, and why
chrome-extension-mv3-workflow 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 12d 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 12d ago First seen · 39 lines · 45 tokens per session scan A bae5982722cb
chrome-extension-mv3-workflow is a skill published in the GitHub repository jgkme/Add-Remote-Torrent (34 stars, last pushed yesterday), licensed GPL-3.0. It adds 45 tokens to every session and 267 once invoked, about $0.0002 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-30.
Other skills, from other repositories
chrome-extension
Use when building or shipping a Manifest V3 browser extension and hitting its quirks — service worker dying and losing state, permission warnings, a Chrome Web Store rejection, content-script/worker/popup messaging, or an MV2-to-V3 migration. NOT a generic web app (that is nextjs), NOT a desktop shell (that is…
browser-extension-patterns
Build browser extensions with Manifest V3 for Chrome, Firefox, and cross-browser compatibility. Covers content scripts, background workers, popup UI, storage APIs, and extension messaging. Triggers on browser extension development, Manifest V3, or Chrome extension requests.
fsb
FSB drives the user's Chrome via the FSB extension and an MCP bridge for live web tasks.
browser-automation
Use this skill when the user asks to interact with a browser, take screenshots, inspect a page, capture network traffic, detect frameworks, click elements, fill forms, record browser sessions, or automate any browser task. Orchestrates Crawlio Browser's 150 browser tools via the search + execute + connecttab interface.
extension-dev
Detect Chrome extension framework/stack, find proper docs, implement features, and debug across service worker, content script, and popup contexts.
extension-create
Auto-scaffold Chrome extensions with WXT or Plasmo. Ask user for name/features, scaffold, configure entrypoints. Use when: create extension, scaffold, new extension.