github-issue-analysis

github-issue-analysis is a skill for Claude Code, Codex from cxcscmu/SkillLearnBench. It costs 29 tokens per session (600 once invoked), scanned A, original, MIT.

A GitHub issue analysis guide for counting issues, finding bug reports from labels, and identifying bugs closed within a month. GitHub issues are records used to track work, problems, and requests.

In plain words
What is it for?
Use it to analyze issue totals, count bug-labeled issues, and measure bugs closed during a specified month.
Why use it?
It turns a dated issue list into consistent measures of reported and resolved bugs.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to analyze issue totals, count bug-labeled issues, and measure bugs…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cxcscmu/skilllearnbench/github-issue-analysis
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 cxcscmu/SkillLearnBench --skill github-issue-analysis
Clone the repo
git clone --depth 1 https://github.com/cxcscmu/SkillLearnBench

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 github-issue-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/cxcscmu/skilllearnbench/github-issue-analysis.svg)](https://agentmods.dev/skills/cxcscmu/skilllearnbench/github-issue-analysis)
Your own site
<a href="https://agentmods.dev/skills/cxcscmu/skilllearnbench/github-issue-analysis"><img src="https://agentmods.dev/badge/skills/cxcscmu/skilllearnbench/github-issue-analysis.svg" alt="Measured on agentmods" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 600 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.00029 $0.00600
Opus 5 $0.00015 $0.00300
Sonnet 5 $0.00006 $0.00120
Haiku 4.5 $0.00003 $0.00060

Measured 3d ago against content hash 8d22b0d248c5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

github-issue-analysis 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 3d 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.

skills/b1-one-shot-claude-sonnet-4-6/github-repo-analytics/github-issue-analysis/SKILL.md · 83 lines

How it starts

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

GitHub Issue Analysis

Overview

Fetch issues created in a date range and compute:

  • Total issue count (excluding PRs)
  • Bug reports: issues with at least one label containing substring bug
  • Resolved bugs: bug report issues closed during the same month

Fetching Issues

# Using gh issue list with search
gh issue list -R cli/cli \
  --search "created:2024-12-01..2024-12-31" \
  --state all \
  --limit 500 \
  --json number,title,labels,state,createdAt,closedAt

Note: gh issue list automatically excludes PRs.

Python: Identify Bug Reports

import json

with open('issues.json') as f:
    issues = json.load(f)

def is_bug(issue):
    """Returns True if any label contains 'bug' as substring (case-insensitive)."""
    return any('bug' in label['name'].lower() for label in issue.get('labels', []))

total = len(issues)
bugs = [i for i in issues if is_bug(i)]

# Closed bugs: bug issues that were closed during the month
# closedAt is within Dec 2024
def closed_in_month(issue, year=2024, month=12):
    if not issue.get('closedAt'):
        return False
    from datetime import datetime, timezone
    dt = datetime.fromisoformat(issue['closedAt'].replace('Z', '+00:00'))
    return dt.year == year and dt.month == month

resolved_bugs = [i for i in bugs if closed_in_month(i)]

print(json.dumps({
    "total": total,
    "bug": len(bugs),
    "resolved_bugs": len(resolved_bugs)
}, indent=2))

Label Matching Examples

Labels that match bug substring:

  • bug
  • type: bug
  • kind/bug
  • bug-report
  • debug — contains bug as substring ✓ (be aware)

For stricter matching (word boundary), use regex:

import re
def is_bug(issue):
    return any(re.search(r'bug', label['name'], re.IGNORECASE)
               for label in issue.get('labels', []))

Important: closedAt vs state

  • closedAt is set when an issue is closed (regardless of month)
  • To find bugs closed during December, filter closedAt to be within Dec 2024
  • An issue created in Dec but closed in Jan would NOT count as resolved_bugs

Read the full file on GitHub · 83 lines

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. 3d ago First seen · 83 lines · 29 tokens per session scan A 8d22b0d248c5

Subscribe to this mod's changes

github-issue-analysis is a skill published in the GitHub repository cxcscmu/SkillLearnBench (83 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 600 once invoked, about $0.0001 per session on Opus 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.

Related

Other skills, from other repositories