Skip to content
Diagnosis · Security

path-types

Choose Rust types for operating system paths across the Codex repository.

Testing what is locked and what isn’t

Works with
ClaudeChatGPTGeminiClaude CodeCodexCursorCopilotGemini CLI
Setup
Upload one file
About a minute in Claude. One command in coding tools.
Contains
Instructions only
Text files — no scripts or programs.
Maintained
Last change 3 Oct 2026
On the repository’s main branch.

What it does

Apply this guidance when defining new types. Change existing code only when explicitly requested, and keep edits minimal and proportional. Treat these rules as the target state of an ongoing migration; if compliance is difficult, ask the user how to proceed.

When your AI uses it

Use when defining new path-bearing types or explicitly migrating existing ones

You don’t need to name it. Ask for the job in your own words — your AI loads the skill when the request matches.

What it can touch

  • No script files in its folder

    Its folder holds text, not programs. It changes how your AI works; it does not bring code of its own.

    How we know

    Listed the one file in the skill’s folder on GitHub; none is a script or program.

  • No known risk pattern found

    Launch7’s automated check read all 1 text files in this skill and matched none of its risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.

    How we know

    Read 2026-10-05, commit c3a2e68 by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.

  • Recently maintained

    Its repository has had changes recently.

    How we know

    Last push to deonmenezes/mantishack: 2026-10-03 (2 days before the scan).

Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check

Add it to your AI

Supported. Upload it once in Claude’s settings. Works on every plan, including Free.

  1. Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.

  2. In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.

  3. Make sure code execution is switched on (Settings → Capabilities). Skills need it.

  4. Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.

How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end

More from deonmenezes

All from this publisher →
  • babysit-pr

    Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is…

    deonmenezesIncludes 2 scripts
  • codex-bug

    Diagnose GitHub bug reports in openai/codex.

    deonmenezesContacts outside web addresses
  • codex-issue-digest

    Run a GitHub issue digest for openai/codex by feature-area labels, all areas, and configurable time windows.

    deonmenezesIncludes 2 scripts
  • findings-spine

    Record and advance every vulnerability finding through the tool-owned mantis_findings service instead of tracking findings in prose

    deonmenezesInstructions only
  • mantis-pipeline

    The master Mantis playbook -- how to run an authorized vulnerability-discovery engagement end to end, which subagent owns each stage, which…

    deonmenezesInstructions only