スキル nex-tab-cost-ext
📦
nex-tab-cost-ext
v1.2 コンテンツリビジョン r1 安全 ⚙️ 外部コマンド🌐 ネットワークアクセス
Plan a Chrome Tab Resource Extension
Resource-heavy browser tabs can be difficult to identify and manage. This guide outlines a no-build extension design with heuristic memory estimates and idle tab controls.
対応: Claude Codex Code(CC)
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
エージェントリクエスト
Review the Skillstore skill "nex-tab-cost-ext" from https://skillstore.io/skills/nexaiguy-nex-tab-cost-ext.md and its manifest at https://skillstore.io/api/skills/nexaiguy-nex-tab-cost-ext/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「nex-tab-cost-ext」を使用しています。 What can I use from this package immediately?
期待される結果:
- The package contains a public guide describing the extension architecture and intended features.
- Extension source, scripts, templates, and the domain weighting database are not included.
- Use the guide for planning; obtain or implement source before attempting to load an extension.
「nex-tab-cost-ext」を使用しています。 Summarize the planned resource dashboard.
期待される結果:
- The design uses estimated memory costs based on domain weight, tab activity, and media playback.
- A toolbar badge indicates total estimated usage, while a popup ranks tabs by estimated impact.
- The example describes closing tabs idle for more than 60 minutes.
- These are documented features, not verified behavior from included extension code.
セキュリティ監査
安全v1 • 2026/11/2 バージョン別レポートを開く
All five static findings are false positives: Markdown formatting and promotional links do not execute commands or perform system reconnaissance. No evidence found of prompt injection, credential access, or data exfiltration in the supplied guide. Extension source is absent, so its runtime behavior and security cannot be assessed.
1
スキャンされたファイル
88
解析済み行数
0
レビュー項目
0
誤検知を無視
リスク要因
⚙️ 外部コマンド (1)
🌐 ネットワークアクセス (3)
最新の完了済み静的・セマンティック監査では、確認済みのセキュリティ検出事項は見つかりませんでした。これは、スキルに副作用がないことを証明するものではありません。
監査者: codex
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/nexaiguy-nex-tab-cost-ext/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/nexaiguy-nex-tab-cost-ext?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/nexaiguy-nex-tab-cost-ext?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/nexaiguy-nex-tab-cost-ext/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/nexaiguy-nex-tab-cost-ext.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
nexaiguy. (2026). nex-tab-cost-ext security audit report (audit version 1) [Author version 1.2]. Skillstore. https://skillstore.io/skills/nexaiguy-nex-tab-cost-ext/audits/1BibTeX形式の引用
@techreport{nexaiguy-nexaiguy-nex-tab-cost-ext-2026,
author = {nexaiguy},
title = {nex-tab-cost-ext security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/nexaiguy-nex-tab-cost-ext/audits/1},
note = {Author version 1.2}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "nex-tab-cost-ext security audit report (audit version 1)"
version: "1.2"
type: report
authors:
- name: "nexaiguy"
date-released: "2026-11-02"
url: "https://skillstore.io/skills/nexaiguy-nex-tab-cost-ext/audits/1"
identifiers:
- type: other
value: "skillstore:nexaiguy-nex-tab-cost-ext:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中 55
アーキテクチャ
85
保守性
87
コンテンツ
65
コミュニティ
83
仕様準拠
作成できるもの
Define an extension prototype
Use the documented architecture and feature list to scope a vanilla JavaScript tab management prototype.
Evaluate tab management features
Compare estimated memory indicators, idle tab controls, achievements, and CSV export when preparing product requirements.
Assess resource estimate limits
Review the heuristic model and distinguish estimated tab costs from measured browser memory usage.
これらのプロンプトを試す
Understand the guide
Summarize the documented Nex Tab Cost design and distinguish included materials from features that require missing extension source.
Prepare feature requirements
Turn the guide into requirements for a tab dashboard, resource badge, and idle tab controls. Mark unspecified behavior as open questions.
Plan heuristic validation
Plan tests for domain weights, tab activity, and media playback estimates. Compare results with Chrome Task Manager without claiming exact equivalence.
Plan a secure implementation
Create an implementation and review plan for the documented MV3 design. Address permissions, tab closure safeguards, CSV privacy, and missing source.
ベストプラクティス
- Confirm that extension source is available before planning installation or deployment.
- Label heuristic memory values as estimates and validate them against measured browser behavior.
- Review permissions and require appropriate safeguards before enabling automated tab closure.
回避
- Treating the public guide as a complete, installable extension package.
- Presenting estimated tab memory as exact Chrome Task Manager measurements.
- Assuming production readiness or store approval without reviewing and testing the actual extension source.
よくある質問
Does this package include a working Chrome extension?
No. The supplied folder contains only a public guide; extension source, scripts, and templates are explicitly excluded.
Does the design measure exact memory usage?
No. It describes heuristic estimates based on domain weight, activity, and media playback, rather than exact Chrome Task Manager measurements.
Does the documented approach require NPM or a build step?
No. The guide describes vanilla JavaScript, HTML, and CSS without a build pipeline.
Can I load this folder through Load Unpacked?
Not as supplied. You need actual extension source, including a valid manifest, before using Chrome's Load Unpacked option.
Which tab management features does the guide describe?
It describes resource badges, a sorted tab dashboard, idle tab closure, achievement badges, and historical usage CSV export.
Has current Chrome Web Store compliance been verified?
No. The guide claims Manifest V3 compatibility, but the absent extension source prevents verification of permissions, runtime behavior, or store compliance.