New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Codex Bug

by deonmenezes in deonmenezes/mantishack

Diagnose GitHub bug reports in openai/codex. An agent skill from deonmenezes/mantishack.

Apache-2.0Auto-check passedTesting & QA

Install Codex Bug

skills CLI
$ npx skills add deonmenezes/mantishack --skill codex-bug -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install deonmenezes/mantishack codex-bug --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/deonmenezes/mantishack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/codex-bug .claude/skills/codex-bug && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
codex-bug
GitHub stars
505
Token cost
~643 tokens
SKILL.md length
339 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
Apache-2.0

At a glance

Diagnose GitHub bug reports in openai/codex. An agent skill from deonmenezes/mantishack.

  • Given a GitHub issue URL from openai/codex and asked to decide next steps such as verifying against the repo
  • SKILL.md covers Overview and Workflow
  • Reaches api.github.com
  • Requesting more info

What it does

Codex Bug is an agent skill from deonmenezes/mantishack. Diagnose GitHub bug reports in openai/codex. Use when given a GitHub issue URL from openai/codex and asked to decide next steps such as verifying against the repo, requesting more info, or explaining why it is not a bug; follow any additional user-provided instructions.

Its SKILL.md is about 640 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering QA and bug reports. It works with GitHub. The licence is Apache-2.0.

When your agent uses it

  • Given a GitHub issue URL from openai/codex and asked to decide next steps such as verifying against the repo
  • Requesting more info
  • Explaining why it is not a bug
  • Follow any additional user-provided instructions

Example prompts

  • “/codex-bug”

What it can do on your machine

Read from SKILL.md and the folder at commit c3a2e68. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • api.github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Codex Bug loads about 643 tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 339 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~70
When it runs · the whole SKILL.md, loaded when a task matches
~643

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from deonmenezes/mantishack at commit c3a2e68, republished under its Apache-2.0 licence (© deonmenezes). 339 words, ~643 tokens.

Download SKILL.mdSave it as .claude/skills/codex-bug/SKILL.md (or your agent's skills folder).
name
codex-bug
description
Diagnose GitHub bug reports in openai/codex. Use when given a GitHub issue URL from openai/codex and asked to decide next steps such as verifying against the repo, requesting more info, or explaining why it is not a bug; follow any additional user-provided instructions.

Codex Bug

Overview

Diagnose a Codex GitHub bug report and decide the next action: verify against sources, request more info, or explain why it is not a bug.

Workflow

  1. Confirm the input
  • Require a GitHub issue URL that points to github.com/openai/codex/issues/….
  • If the URL is missing or not in the right repo, ask the user for the correct link.
  1. Network access
  • Always access the issue over the network immediately, even if you think access is blocked or unavailable.
  • Prefer the GitHub API over HTML pages because the HTML is noisy:
    • Issue: https://api.github.com/repos/openai/codex/issues/<number>
    • Comments: https://api.github.com/repos/openai/codex/issues/<number>/comments
  • If the environment requires explicit approval, request it on demand via the tool and continue without additional user prompting.
  • Only if the network attempt fails after requesting approval, explain what you can do offline (e.g., draft a response template) and ask how to proceed.
  1. Read the issue
  • Use the GitHub API responses (issue + comments) as the source of truth rather than scraping the HTML issue page.
  • Extract: title, body, repro steps, expected vs actual, environment, logs, and any attachments.
  • Note whether the report already includes logs or session details.
  • If the report includes a thread ID, mention it in the summary and use it to look up the logs and session details if you have access to them.
  1. Summarize the bug before investigating
  • Before inspecting code, docs, or logs in depth, write a short summary of the report in your own words.
  • Include the reported behavior, expected behavior, repro steps, environment, and what evidence is already attached or missing.
  1. Decide the course of action
  • Verify with sources when the report is specific and likely reproducible. Inspect relevant Codex files (or mention the files to inspect if access is unavailable).
  • Request more information when the report is vague, missing repro steps, or lacks logs/environment.
  • Explain not a bug when the report contradicts current behavior or documented constraints (cite the evidence from the issue and any local sources you checked).
  1. Respond
  • Provide a concise report of your findings and next steps.

© deonmenezes, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .codex/skills/codex-bug of deonmenezes/mantishack.

Open the folder on GitHubat commit c3a2e68

Compare with similar skills

Codex Bug next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Codex Bug compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Codex Bug this skilldeonmenezes/mantishack505—~643Automated safety check: PassApache-2.0
Weavebench Cua ReproduceAMAP-ML/LongHorizon-Harness1.7k—~1.6kAutomated safety check: PassMIT
Evidence-Driven Testingmichaelshimeles/skills1.3k1 repos~3.9kAutomated safety check: PassNone
Create GitHub IssueNVIDIA/OpenShell15k—~1.7kAutomated safety check: PassApache-2.0
Triage IssuesClickHouse/clickhouse-java1.6k—~904Automated safety check: PassApache-2.0
Gentle AI Issue CreationGentleman-Programming/gentle-shell1.2k—~2.5kAutomated safety check: PassApache-2.0

Similar skills

  • Weavebench Cua Reproduce

    AMAP-ML/LongHorizon-Harness

    Reproduce CUA-Harness experiments on WeaveBench from a GitHub checkout.

    1.7k GitHub stars~1.6k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • Evidence-Driven Testing

    michaelshimeles/skills

    Records an annotated screen recording of the agent testing an app hands-on, then posts the video and a results summary to the PR and tracker issue.

    1.3k GitHub starsUsed in 1 repo~3.9k tokens
    Testing & QAAuto-check passed

  • Create GitHub Issue

    NVIDIA/OpenShell

    Official

    Create GitHub issues using the gh CLI. An agent skill from NVIDIA/OpenShell.

    15k GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed

  • Triage Issues

    ClickHouse/clickhouse-java

    Analyzes a single GitHub issue at a time. An agent skill from ClickHouse/clickhouse-java.

    1.6k GitHub stars~904 tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Gentle AI Issue Creation

    Gentleman-Programming/gentle-shell

    Create and triage GitHub issues from repository evidence. An agent skill from Gentleman-Programming/gentle-shell.

    1.2k GitHub stars~2.5k tokensUpdated today
    Testing & QAAuto-check passed

  • Termio Bug Report

    termio-sh/termio

    Diagnose a termio hang, beachball, crash, or 'it froze again' from the evidence macOS and termio actually leave behind — live process samples, crash and CPU-burn reports, the unified log, the…

    540 GitHub stars~1.9k tokensUpdated yesterday
    Testing & QAAuto-check passed

More from deonmenezes/mantishack

All 11 skills in this repo

  • Codex Issue Digest

    deonmenezes/mantishack

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

    505 GitHub stars~2.3k tokensUpdated 5 days ago
    Auto-check passed

  • Detection Breadth

    deonmenezes/mantishack

    When and how to reach for the companion detectors -- bandit (Python SAST) and trivy (deps + secrets + IaC misconfig) -- alongside the core semgrep/CodeQL/osv/trufflehog toolchain

    505 GitHub stars~510 tokensUpdated 5 days ago
    Auto-check passed

  • HTTP Evidence

    deonmenezes/mantishack

    Turn a captured HTTP request/response into a bounded, redacted evidence pack with a stable request-ref using the mantishttpaudit MCP server, instead of pasting raw traffic into a finding

    505 GitHub stars~455 tokensUpdated 5 days ago
    Auto-check passed

  • Program Analysis

    deonmenezes/mantishack

    Use astgrepscan, sourcesinkscan, and smtcheckreachability (mantisprogramanalysis MCP server) to move a candidate toward a proven-reachable finding

    505 GitHub stars~551 tokensUpdated 5 days ago
    Auto-check passed

  • Canary Tripwire Response

    deonmenezes/mantishack

    What to do if a mantiscanary decoy tool ever shows up as tempting or gets called -- treat it as a security incident, not a normal tool result

    505 GitHub stars~376 tokensUpdated 5 days ago
    Auto-check passed

  • Codeql Audit

    deonmenezes/mantishack

    Build a CodeQL database and run dataflow-backed query-suite analysis via the mantiscodeql MCP server

    505 GitHub stars~325 tokensUpdated 5 days ago
    Auto-check passed

Works with

Categories

Questions about Codex Bug

What does Codex Bug do?

Diagnose GitHub bug reports in openai/codex. An agent skill from deonmenezes/mantishack. Codex Bug is an agent skill from deonmenezes/mantishack. Diagnose GitHub bug reports in openai/codex.

When should I use Codex Bug?

Codex Bug fits situations like: given a GitHub issue URL from openai/codex and asked to decide next steps such as verifying against the repo; requesting more info; explaining why it is not a bug; follow any additional user-provided instructions.

How do I install Codex Bug in Claude Code?

Run `npx skills add deonmenezes/mantishack --skill codex-bug -a claude-code`. Or copy the skill folder (.codex/skills/codex-bug in deonmenezes/mantishack) into .claude/skills/codex-bug in your project. Claude Code loads it when a task matches its description.

How do I install Codex Bug in Codex?

Run `npx skills add deonmenezes/mantishack --skill codex-bug -a codex`. Or copy the skill folder (.codex/skills/codex-bug in deonmenezes/mantishack) into .agents/skills/codex-bug in your project. Codex loads it when a task matches its description.

Can I use Codex Bug in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add deonmenezes/mantishack --skill codex-bug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/codex-bug, .gemini/skills/codex-bug, .github/skills/codex-bug and .opencode/skills/codex-bug in your project.

What does Codex Bug need to run?

SKILL.md names no scripts, command-line tools or credentials: Codex Bug is instructions for the agent only.

Does Codex Bug access the network?

SKILL.md names 1 domain. In commands or code: api.github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Codex Bug safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Codex Bug use?

Codex Bug is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Codex Bug use?

About 643 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Codex Bug?

Skills that share tags, products or a category with Codex Bug: Weavebench Cua Reproduce (AMAP-ML/LongHorizon-Harness, 1.7k stars), Evidence-Driven Testing (michaelshimeles/skills, 1.3k stars), Create GitHub Issue (NVIDIA/OpenShell, 15k stars) and Triage Issues (ClickHouse/clickhouse-java, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Codex Bug?

deonmenezes (a GitHub user) maintains it in deonmenezes/mantishack, which has 505 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 3, 2026.

Source: deonmenezes/mantishack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.