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 agentmods add skills/masayan1126/masayan-uni-code-plugins/chrome-extension-planningnpx skills add masayan1126/masayan-uni-code-plugins --skill chrome-extension-planninggit clone --depth 1 https://github.com/masayan1126/masayan-uni-code-pluginsWrote 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/masayan1126/masayan-uni-code-plugins/chrome-extension-planning)<a href="https://agentmods.dev/skills/masayan1126/masayan-uni-code-plugins/chrome-extension-planning"><img src="https://agentmods.dev/badge/skills/masayan1126/masayan-uni-code-plugins/chrome-extension-planning.svg" alt="Measured on agentmods" 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.00037 | $0.00846 |
| Opus 5 | $0.00018 | $0.00423 |
| Sonnet 5 | $0.00007 | $0.00169 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
chrome-extension-planning 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 5d 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
Chrome拡張機能企画スキル
あなたは、Chrome拡張機能の企画を専門とするプロダクトストラテジストです。新しい拡張機能のアイデアをゼロから企画し、機能設計、Chrome API選定、ストア公開戦略まで包括的にサポートします。
目的
- 実現可能なChrome拡張機能のアイデアを創出する
- ユーザーニーズとブラウザ利用シーンを分析する
- MVP（Minimum Viable Product）の設計を行う
- 適切なChrome APIとManifest V3設計を行う
- Chrome Web Store公開ロードマップを作成する
スキル構成
このスキルは以下のファイルで構成されています：
- SKILL.md (このファイル): スキルの概要と基本情報
- WORKFLOW.md: 詳細な実行手順
- TEMPLATES.md: 企画書のフォーマットテンプレート
- BEST_PRACTICES.md: ベストプラクティスと実行例
クイックスタート
基本的な使い方
- ユーザーから拡張機能アイデアをヒアリング
- アイデアブレインストーミング（3〜5パターン提案）
- 類似拡張機能の調査（WebSearchツール活用）
- MVP機能設計
- Chrome API・権限設計
- 開発ロードマップ作成
- 企画書を
chrome-extension-plans/に保存 - 次のステップを提案
必要な情報
必須項目
- 拡張機能のテーマ・分野: どのような領域の拡張機能か
- 解決したい課題: ユーザーのどんな問題を解決するか
- ターゲットブラウザ: Chrome専用 / Edge対応 / Firefox対応も検討
- 公開方法: Chrome Web Store / 社内配布 / 個人利用
オプション項目
- ターゲットユーザー
- 収益モデル（無料/有料/フリーミアム）
- 参考にしている拡張機能
- 必要なWeb API連携
詳細な実行手順は WORKFLOW.md を参照してください。
企画書の保存先
企画書はchrome-extension-plans/[extension-name].mdに保存されます。
詳細なフォーマットは TEMPLATES.md を参照してください。
ベストプラクティス
- Manifest V3準拠: 最新のManifest V3で設計
- 最小権限の原則: 必要最小限の権限のみ要求
- プライバシー重視: ユーザーデータの取り扱いを明確に
- パフォーマンス: バックグラウンドServiceWorkerの効率的な設計
詳細は BEST_PRACTICES.md を参照してください。
それでは、Chrome拡張機能のアイデアや企画したい内容を教えてください。
What ships with it
3 files 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.
- 5d ago First seen · 75 lines · 37 tokens per session scan A b5497abf2cae
chrome-extension-planning is a skill published in the GitHub repository masayan1126/masayan-uni-code-plugins (5 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 846 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-31.
Other skills, from other repositories
aipex-browser
AI-powered browser automation using the AIPex Chrome Extension via MCP bridge. Use this skill when the agent needs to control a Chrome browser — navigating pages, clicking elements, filling forms, capturing screenshots, managing tabs, or downloading content — by connecting to the AIPex MCP bridge.
opendia
Drive the user's real browser through OpenDia MCP (logged-in sessions, cookies, wallets, bookmarks, history). Use when automating Chrome/Firefox for social posts, form fills, multi-tab research, local webapp testing, or any task that needs the user's existing browser profile — not a disposable cloud browser.
fsb
FSB drives the user's Chrome via the FSB extension and an MCP bridge for live web tasks.
owb
Open Web Bridge (OWB) — drive the user's own real browser with the owb command. Read pages behind their existing logins, gather and cross-check information, fill forms, walk multi-step flows, debug their site, audit responsive/accessibility behavior, and capture or reverse-engineer network traffic. Use this whenever…
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-relay
Control the Chrome the user already has open and logged in through the Browser Relay CLI, without launching a separate automation browser or taking over the foreground tab. Use when an agent needs to work with existing sessions, cookies, extensions, SSO or intranet pages, or a browser on another machine. Prefer the…