A command for investigating a GitHub issue, which is a reported bug, request, or task. It reads the issue, checks the referenced code, verifies whether the report is still accurate, and can offer to carry out the work.

Use it with an issue number to inspect the report, compare expected and actual behavior, check its current status, and optionally execute the resulting task.

It reduces guesswork by requiring the issue and relevant code to be examined before conclusions are made.

handle — Command by bengous

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.

agentmods

npx agentmods add commands/bengous/claude-code-plugins/handle

Clone the repo

git clone --depth 1 https://github.com/bengous/claude-code-plugins

Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 675 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00014	$0.00675
Opus 5	$0.00007	$0.00338
Sonnet 5	$0.00003	$0.00135
Haiku 4.5	$0.00001	$0.00068

Measured yesterday against content hash 822cd379d37c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

handle 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 yesterday.

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.

git-tools/commands/handle.md · 110 lines

How it starts

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

Issue Handler

Usage: /handle <issue-number>

Investigate a GitHub issue, verify it's still valid, and offer to execute it.

Critical Rule

Do not speculate about code you haven't read. If the issue mentions a file, function, or pattern—read it before making any claims.

Step 1: Fetch

gh issue view $1 --json number,title,body,state,author,createdAt,labels,comments

If the issue doesn't exist or is closed, report that and stop.

Step 2: Extract Claims

From the issue body, identify:

The problem: What bug, missing feature, or behavior is described?
Code references: Any file paths, function names, error messages, or snippets mentioned
Expected vs actual: What should happen vs what happens?
Reproduction: Steps to trigger the issue, if provided

Step 3: Investigate

For each code reference extracted above:

Locate it: Glob for file paths, Grep for function/error names
Read it: Open the file, read the relevant section
Understand context: Read surrounding code to grasp current behavior

If the issue mentions no specific files, search for keywords from the problem description.

Step 4: Fact-Check

Issues become stale. Code changes. PRs merge without linking. Verify before investing effort.

Check 1: Does the problem exist?

For bugs: Can you confirm the faulty behavior in current code?
For features: Is the capability truly missing?

Check 2: Already fixed?

git log --oneline -20 -- <relevant-file>

Look for commits that address this. Check if related PRs were merged.

Check 3: Outdated?

Has the relevant code been refactored or removed?
Does the described behavior no longer apply?

Step 5: Report

If INVALID or OUTDATED:

## Issue #N: [Title]

**Status: INVALID** (or OUTDATED)

**Why:** [One sentence explanation]

**Evidence:**
- [Quote from code, commit hash, or specific finding]

**Recommendation:** Close with reason: [completed | not_planned]

Read the full file on GitHub · 110 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.

yesterday First seen · 110 lines · 14 tokens per session scan A 822cd379d37c

Subscribe to this mod's changes

handle is a command published in the GitHub repository bengous/claude-code-plugins (4 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 675 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-08-31.

Debugging Git and workflow Research automation claude-code developer-tools workflow

handle

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Issue Handler

Critical Rule

Step 1: Fetch

Step 2: Extract Claims

Step 3: Investigate

Step 4: Fact-Check

Step 5: Report

What this file has done since we first saw it

Other commands, from other repositories

pr-address

plan-save

enforce_standards

OPSX: Sync

context

OPSX: Verify