📦

mantis-patch

Name: mantis-patch
Author: google

Révision du contenu r1 Risque élevé ⚙️ Commandes externes📁 Accès au système de fichiers

Generate and Verify Minimal Security Patches

Security fixes can fail when verification uses stale code or broken test harnesses. This skill guides minimal patches with snapshot checks, baseline tests, and independent re-attacks.

Prend en charge: Claude Codex Code(CC)

⚠️ 38 Médiocre

Maintain this Skill? Claim it ⚠️ 38 Médiocre

Arrêtez-vous et demandez confirmation avant l’installation.

Examinez le plan et obtenez le consentement explicite de l’utilisateur avant de modifier des fichiers.

Installer avec mon Agent

Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.

Demande d’agent

Review the Skillstore skill "mantis-patch" from https://skillstore.io/skills/google-mantis-patch.md and its manifest at https://skillstore.io/api/skills/google-mantis-patch/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.

Ressources lisibles par les agents

Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.

Détail Markdown GET /skills/google-mantis-patch.md manifest signé GET /api/skills/google-mantis-patch/manifest lockfile signé GET /api/skills/google-mantis-patch/lockfile

Tester

Utilisation de « mantis-patch ». Verify a bounds-check patch for an existing reproduced finding.

Résultat attendu:

Illustrative result: Patch verification passed for the current snapshot and tested vulnerability.
The unpatched baseline triggered the issue; the patched build compiled and the benign control reached the target without crashing.
The attack and three independent variants did not trigger the original vulnerability class.
A unified diff and verification history were recorded; the original source remained unchanged.

Utilisation de « mantis-patch ». Assess a reproduced firmware issue without source code.

Résultat attendu:

Illustrative result: Mitigation proposed.
No binary modification was attempted.
Restrict access to the affected interface and pursue a vendor-supported firmware correction.
The finding record contains mitigation guidance rather than a source diff.

Utilisation de « mantis-patch ». Verify a patch when independent re-attack testing times out.

Résultat attendu:

Illustrative result: Verification incomplete.
Initial verification passed, but the independent re-attack did not complete.
No verified-secure claim was recorded; the finding remains eligible for further verification.

Audit de sécurité

Risque élevé

v1 • 04/10/2026 Ouvrir le rapport versionné

All 250 static alerts are false positives: their context shows Markdown formatting, workflow metadata, temporary copies, and verification checks rather than the reported threats. Two semantic risks remain: stored reproducer commands lack required host confinement, and helper reuse relies on a forgeable version comment. No evidence found of malicious prompt injection, credential collection, or deliberate data exfiltration.

Fichiers analysés

825

Lignes analysées

Éléments à examiner

Faux positifs ignorés

Préoccupations de sécurité confirmées (2)

Élevé

SKILL.md:350-376 SKILL.md:378-396 SKILL.md:506-515

Stored Commands Lack Mandatory Host Isolation

The skill executes run_command from finding records after path substitution. Mandatory shadow copies protect source changes but do not confine process permissions or network access. If commands or reproducers are compromised, they can access host resources unless the caller supplies an additional sandbox.

Stored-command execution is explicit, while containers and namespaces are optional alternatives to source copies. Host confinement is not required; exploitation depends on compromised inputs.

Élevé

SKILL.md:733-743

Version Marker Used To Trust Executable Helpers

Helper reuse checks its first line for MANTIS_HELPER_VERSION = 2, then instructs execution of the existing script. An attacker with helper write access can preserve that comment while replacing executable content. The version check does not establish helper integrity or provenance.

The instructions explicitly permit execution after a first-line marker check. The integrity gap is clear; exploitation requires control over the helper file.

Facteurs de risque

⚙️ Commandes externes (50)

📁 Accès au système de fichiers (13)

SKILL.md:43 SKILL.md:44 SKILL.md:98 SKILL.md:104 SKILL.md:122 SKILL.md:124 SKILL.md:231 SKILL.md:413 SKILL.md:447 SKILL.md:470 SKILL.md:119 SKILL.md:351 SKILL.md:387

Audité par: codex

Partager et citer ce rapport

Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.

Ouvrir le rapport versionné

Copier le lien du rapport

https://skillstore.io/skills/google-mantis-patch/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Badge Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/google-mantis-patch/security.svg)](https://skillstore.io/skills/google-mantis-patch?utm_source=security_passport_badge)

Badge HTML

<a href="https://skillstore.io/skills/google-mantis-patch?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/google-mantis-patch/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Carte intégrable

<iframe src="https://skillstore.io/embed/skills/google-mantis-patch.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Citations académiques (APA · BibTeX · CFF)

Citation APA

google. (2026). mantis-patch security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/google-mantis-patch/audits/1

Citation BibTeX

@techreport{google-google-mantis-patch-2026,
  author = {google},
  title = {mantis-patch security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/google-mantis-patch/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-patch 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-patch/audits/1"
identifiers:
  - type: other
    value: "skillstore:google-mantis-patch:audit:1"
    description: "Skillstore immutable audit report identifier"

Score Skillstore

Pourquoi ce score Niveau de confiance des preuves: Moyen

Architecture

Maintenabilité

Contenu

Communauté

Conformité aux spécifications

Ce que vous pouvez créer

Remediate Reproduced Vulnerabilities

Create a minimal source fix and collect baseline, benign-control, and re-attack results for an existing reproduced finding.

Review Fixes After Source Changes

Reopen stale findings and rebase eligible archived patches onto a new snapshot before verification.

Assess Binary-Only Mitigations

Produce mitigation recommendations for firmware or compiled targets when source code is unavailable.

Essayez ces prompts

Inspect Ready Findings

Use mantis-patch to identify eligible findings in [state_root]. Summarize required inputs and blockers without running commands or editing source.

Patch One Reproduced Finding

Patch finding [finding_id] using snapshot [snapshot_root] and state directory [state_root]. Review commands, verify helper integrity, and require a restricted execution environment.

Verify A Patch Thoroughly

Verify finding [finding_id] inside a restricted execution environment. Require baseline evidence, matching sanitizer flags, benign controls, and independent re-attacks; report missing evidence.

Rebase Archived Fixes

Review stale findings against [snapshot_root] and verify helper integrity. Rebase only eligible fixes, test in restricted environments, extract diffs, and roll back changes.

Bonnes pratiques

Review finding records and reproducer commands before execution in a restricted environment without host secrets.
Use pinned snapshots and private shadow copies to keep baseline code unchanged.
Verify complete helper content and require baseline evidence, benign controls, consistent sanitizers, and independent re-attacks.

Éviter

Run unreviewed commands from finding records directly on a sensitive host.
Trust an existing helper solely because its first line contains the expected version marker.
Claim verified security after missing files, failed builds, stale baselines, or incomplete re-attacks.

Foire aux questions

What inputs does this skill require?

It requires Mantis finding records, target source or binary artifacts, and reproducer details for runnable verification.

Does it discover new vulnerabilities?

No. It targets reproduced findings and exploit-chain records rather than initial vulnerability research.

Does it leave fixes applied to the source tree?

No. It extracts patch diffs and restores the original source or removes temporary shadows after processing.

What happens when source code is unavailable?

It proposes mitigation guidance and does not attempt binary modification.

What is required for verified-secure status?

Baseline evidence, successful compilation, benign controls, consistent sanitizer settings, and independent re-attacks are required. This status does not guarantee absence of other vulnerabilities.

Are temporary shadow directories a security sandbox?

No. They isolate source changes, not host access. Use restricted execution and review stored commands and helpers.