report-issue

A command that opens a GitHub issue from a written description. GitHub issues are shared records for bugs, feature requests, and questions about a repository.

In plain words
What is it for?
Use it to report a bug, request an enhancement, or ask a question in a GitHub repository, with duplicate checking and issue classification.
Why use it?
It helps create a consistent issue after checking authentication, repository support, templates, and possible duplicate issues.

Command

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/damusix/atomic-claude/report-issue
Clone the repo
git clone --depth 1 https://github.com/damusix/atomic-claude
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 776 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.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.00776
Opus 5 $0.00011 $0.00388
Sonnet 5 $0.00004 $0.00155
Haiku 4.5 $0.00002 $0.00078

Measured 3d ago against content hash 04e14ee028c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

report-issue 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.

context/commands/report-issue.md · 102 lines

How it starts

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

Prereqs

  • command -v gh — if missing: tell user to install (brew install gh / winget install --id GitHub.cli / https://cli.github.com/) then gh auth login. Stop.
  • gh auth status — if unauthed: tell user gh auth login. Stop.

Steps

  1. Read user's description. Classify: bug vs feature/enhancement vs question. If ambiguous, ask once.
  2. Check repo: gh repo view --json nameWithOwner,hasIssuesEnabled. If issues disabled, stop.
  3. List existing issue templates: gh issue create --help notes --template. Check .github/ISSUE_TEMPLATE/ — if templates exist, prefer --template <file> and let user fill in via editor. Otherwise build body inline.
  4. Search for duplicates: gh issue list --search "<key terms>" --state all --limit 5. If close match exists, surface URL + ask before opening new.
  5. Draft title — imperative for features (Add X), declarative for bugs (X crashes when Y). ≤70 chars. No "Bug:" / "Feature:" prefix unless repo convention demands.
  6. Draft body per shape below (HEREDOC). Atomic tone — drop filler, exact symbols in backticks, no hedging, no AI bylines. Redact per the Privacy section as you draft — never write raw PII, secrets, or third-party identifiers into the body.
  7. Map classification → label: bugbug, feature/enhancementenhancement, questionquestion. Verify the label exists on the repo first: gh label list --search <name>. Skip the label if it doesn't exist (don't auto-create). User-specified labels stack on top.
  8. Preview: print the full rendered issue — title, body, target repo, labels — and get an explicit go-ahead from the user before creating. See Privacy.
  9. gh issue create --title "<title>" --body "$(cat <<'EOF' … EOF)" [--label <classified>] [--label <user-specified>].
  10. Print issue URL.

{{ template "report-issue-privacy" . }}

Body shapes

Bug

## Summary

<one-line statement of what's broken>

## Repro

1. <step>
2. <step>
3. <step>

## Expected

<what should happen>

## Actual

<what happens, including exact error message in a code block>

## Environment

- Version / commit: <x>
- OS: <x>
- Runtime: <x>

Read the full file on GitHub · 102 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 · 102 lines · 22 tokens per session scan A 04e14ee028c4

Subscribe to this mod's changes

report-issue is a command published in the GitHub repository damusix/atomic-claude (83 stars, last pushed 9d ago), licensed MIT. It adds 22 tokens to every session and 776 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-30.