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/ryoha000/launchergWrote 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/rules/ryoha000/launcherg/20-extension-workflow)<a href="https://agentmods.dev/rules/ryoha000/launcherg/20-extension-workflow"><img src="https://agentmods.dev/badge/rules/ryoha000/launcherg/20-extension-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/rules/ryoha000/launcherg/20-extension-workflow"><img src="https://agentmods.dev/badge/rules/ryoha000/launcherg/20-extension-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.00000 | $0.00303 |
| Opus 5 | $0.00000 | $0.00151 |
| Sonnet 5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
20-extension-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 today.
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
ブラウザ拡張 ワークフロー（background / content-scripts / shared）
- チェック:
- ルートから
task check:browser-extensionを実行 - パッケージ単位の実行が必要な場合は該当の
check:browser-extension:*を選択
- ルートから
- パッケージ単位:
- background:
browser-extension/background - content-scripts:
browser-extension/content-scripts（dmm,dlsiteはそれぞれでチェック） - shared:
browser-extension/shared
- background:
- Chrome APIの型:
as anyを避け、必要に応じて型定義パッケージを導入。 - ロガー/ユーティリティ: 共有モジュールを優先利用し、重複実装を避ける。
- コマンド実行ポリシー: ブラウザ拡張のまとめチェック・ビルドは
task経由で実行（check:*/build:*）。
参照
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.
- today First seen · 19 lines · 0 tokens per session scan A c68125b53b5b
20-extension-workflow is a cursor rule published in the GitHub repository ryoha000/launcherg (37 stars, last pushed 5mo ago), licensed Unlicense. It costs nothing until one of its globs matches a file; then it loads 303 tokens. 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-09-12.
Other cursor rules, from other repositories
chrome-extension
You are an expert Chrome extension developer, proficient in JavaScript/TypeScript, browser extension APIs, and web development.
javascript-chrome-apis-cursorrules-prompt-file
Cursor rules for JavaScript development with Chrome APIs integration.
testing
Comprehensive Testing Best Practices for Svelte 5 + vitest-browser-svelte.
chrome-extension
Chrome extension (Manifest V3) — structure, dev/prod URL toggle, popup design, extraction strategy, InputMethod.EXTENSION backend integration.
ui-and-styling-rules
User-interface and CSS guidelines for Chrome extension pop-ups and settings pages, covering responsive layouts and consistent styling.
rules--client-event-listeners
Use useSWRSubscription() to share global event listeners across component instances.