issue-discover

issue-discover is a skill for Claude Code, Codex from catlog22/Claude-Code-Workflow. It costs 63 tokens per session (3,274 once invoked), scanned A, original, MIT.

An issue-management skill for creating issues manually or finding possible issues through structured analysis of a request or project.

In plain words
What is it for?
It is for creating issues, discovering issues from multiple viewpoints, and exploring a prompt to identify work that should be tracked.
Why use it?
It helps turn observations and requirements into trackable work instead of leaving them in conversation notes.

Skill for Claude CodeCodex

Written for Claude Code and Codex: allowed-tools in frontmatter, but also installed under .codex/. Also seen: mentions subagents.

Good fit It is for creating issues, discovering issues from multiple viewpoints, and exploring a prompt to identify work that should be tracked.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/catlog22/claude-code-workflow/issue-discover
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add catlog22/Claude-Code-Workflow --skill issue-discover
Clone the repo
git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for issue-discover

README.md
[![agentmods](https://agentmods.dev/badge/skills/catlog22/claude-code-workflow/issue-discover/github.svg)](https://agentmods.dev/skills/catlog22/claude-code-workflow/issue-discover)
Your own site
<a href="https://agentmods.dev/skills/catlog22/claude-code-workflow/issue-discover"><img src="https://agentmods.dev/badge/skills/catlog22/claude-code-workflow/issue-discover/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for issue-discover

Your own site · 80×15
<a href="https://agentmods.dev/skills/catlog22/claude-code-workflow/issue-discover"><img src="https://agentmods.dev/badge/skills/catlog22/claude-code-workflow/issue-discover.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,274 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00063 $0.03274
Opus 5.5 $0.00025 $0.01310
Sonnet 5.5 $0.00013 $0.00655
Haiku 4.5 $0.00006 $0.00327

Measured 1mo ago against content hash b3aa08e3e14e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

issue-discover scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.codex/skills/issue-discover/SKILL.md · 374 lines

How it starts

The opening of the file, as written. The whole thing — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Issue Discover

Unified issue discovery and creation skill covering three entry points: manual issue creation, perspective-based discovery, and prompt-driven exploration.

Architecture Overview

┌─────────────────────────────────────────────────────────────────┐
│  Issue Discover Orchestrator (SKILL.md)                          │
│  → Action selection → Route to phase → Execute → Summary         │
└───────────────┬─────────────────────────────────────────────────┘
                │
                ├─ request_user_input: Select action
                │
    ┌───────────┼───────────┬───────────┐
    ↓           ↓           ↓           │
┌─────────┐ ┌─────────┐ ┌─────────┐   │
│ Phase 1 │ │ Phase 2 │ │ Phase 3 │   │
│  Create │ │Discover │ │Discover │   │
│   New   │ │  Multi  │ │by Prompt│   │
└─────────┘ └─────────┘ └─────────┘   │
     ↓           ↓           ↓          │
  Issue      Discoveries  Discoveries   │
(registered)  (export)    (export)      │
     │           │           │          │
     │           ├───────────┤          │
     │           ↓                      │
     │     ┌───────────┐               │
     │     │  Phase 4  │               │
     │     │Quick Plan │               │
     │     │& Execute  │               │
     │     └─────┬─────┘               │
     │           ↓                      │
     │     .task/*.json                 │
     │           ↓                      │
     │     Direct Execution             │
     │           │                      │
     └───────────┴──────────────────────┘
                  ↓ (fallback/remaining)
          issue-resolve (plan/queue)
                  ↓
            /issue:execute

Key Design Principles

  1. Action-Driven Routing: request_user_input selects action, then load single phase
  2. Progressive Phase Loading: Only read the selected phase document
  3. CLI-First Data Access: All issue CRUD via ccw issue CLI commands
  4. Auto Mode Support: -y flag skips action selection with auto-detection
  5. Subagent Lifecycle: Explicit lifecycle management with spawn_agent → wait_agent → close_agent
  6. Role Path Loading: Subagent roles loaded via path reference in MANDATORY FIRST STEPS

Read the full file on GitHub · 374 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 374 lines · 63 tokens per session scan A b3aa08e3e14e

Subscribe to this mod's changes

issue-discover is a skill published in the GitHub repository catlog22/Claude-Code-Workflow (2,124 stars, last pushed 4mo ago), licensed MIT. It adds 63 tokens to every session and 3,274 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.