mantis-dedupe
Consolidate Duplicate Security Findings
Repeated security findings increase review effort and can obscure regressions. This skill guides consolidation while preserving provenance, active regression candidates, and transaction history.
インストール前に停止して確認を求めてください。
計画を確認し、ファイルを変更する前にユーザーの明示的な同意を得てください。
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "mantis-dedupe" from https://skillstore.io/skills/google-mantis-dedupe.md and its manifest at https://skillstore.io/api/skills/google-mantis-dedupe/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「mantis-dedupe」を使用しています。 Two findings describe the same flaw at the same line and share discovery provenance.
期待される結果:
- One primary finding retains its identifier and the highest reported severity.
- Descriptions, code paths, and history are consolidated.
- The duplicate is staged with linkage to the primary finding, and its move is logged.
「mantis-dedupe」を使用しています。 A new finding matches a resolved archived issue, but their discovery snapshots differ.
期待される結果:
- The new finding remains active.
- A possible duplicate hint references the archived finding.
- History records a possible regression; the finding is not moved to staging.
「mantis-dedupe」を使用しています。 Two findings have matching signatures and titles but identify different lines in the same file.
期待される結果:
- The findings remain separate because their line-inclusive locations differ.
- Signature agreement alone does not justify a duplicate status or staged removal.
セキュリティ監査
高リスクThe 160 static alerts describe Markdown notation, legitimate workspace operations, and defensive snapshot checks rather than the alleged execution or reconnaissance threats. Semantic review found unsafe helper reuse and potential disclosure of sensitive vulnerability summaries through external embeddings. No evidence found of malicious intent or instructions to manipulate this audit.
確認済みのセキュリティ上の懸念 (2)
リスク要因
⚙️ 外部コマンド (50)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/google-mantis-dedupe/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/google-mantis-dedupe?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/google-mantis-dedupe?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/google-mantis-dedupe/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/google-mantis-dedupe.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形式の引用
google. (2026). mantis-dedupe security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/google-mantis-dedupe/audits/1BibTeX形式の引用
@techreport{google-google-mantis-dedupe-2026,
author = {google},
title = {mantis-dedupe security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/google-mantis-dedupe/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "mantis-dedupe security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "google"
date-released: "2026-10-04"
url: "https://skillstore.io/skills/google-mantis-dedupe/audits/1"
identifiers:
- type: other
value: "skillstore:google-mantis-dedupe:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Prepare a Security Review Queue
Consolidate repeated reports at identical locations while retaining severity, supporting details, and review history.
Preserve Regression Candidates Across Passes
Compare new findings with archived records and retain possible regressions when discovery snapshots differ.
Maintain Traceable Finding Pipelines
Process large queues with grouped comparisons, provenance checks, staged duplicates, and transaction records.
これらのプロンプトを試す
Review the existing findings and identify duplicate candidates. Explain the matching evidence before changing any files.
Consolidate findings with identical line-inclusive locations and matching titles. Preserve provenance and history, stage duplicates, and summarize changes.
Compare current and archived findings using pairwise discovery provenance. Keep unmatched findings active and annotate regressions against resolved archived issues.
Group findings by component, verify helpers before execution, and apply snapshot-gated matching. Require approval before external embeddings and summarize staged moves.
ベストプラクティス
- Back up workspace state and review matching evidence before applying consolidation.
- Verify helper contents independently before execution; a version comment does not establish trust.
- Approve external embedding use explicitly and redact sensitive vulnerability details before transmission.
回避
- Marking findings as duplicates based only on signatures, without line-inclusive location agreement.
- Suppressing potential regressions or merging findings from different discovery versions.
- Executing existing helpers solely because their version comments match.