mach12:gh-issue-read

mach12:gh-issue-read is a command for Claude Code from LeanAndMean/scramjet. It costs 20 tokens per session (913 once invoked), scanned A, original, Apache-2.0.

A command that retrieves a GitHub issue’s title, description, dates, and complete comment history. It can also look for a specific hidden HTML marker in the discussion.

In plain words
What is it for?
Use it to inspect an issue before planning or coding, or to find marked information such as plans or decisions.
Why use it?
It gathers the full issue context in one place, including decisions and requirements that may be buried in comments.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to inspect an issue before planning or coding, or to find marked information such as plans or decisions.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/leanandmean/scramjet/mach12-gh-issue-read
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.

Clone the repo
git clone --depth 1 https://github.com/LeanAndMean/scramjet

Made for: Claude Code.

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 mach12:gh-issue-read

README.md
[![agentmods](https://agentmods.dev/badge/commands/leanandmean/scramjet/mach12-gh-issue-read/github.svg)](https://agentmods.dev/commands/leanandmean/scramjet/mach12-gh-issue-read)
Your own site
<a href="https://agentmods.dev/commands/leanandmean/scramjet/mach12-gh-issue-read"><img src="https://agentmods.dev/badge/commands/leanandmean/scramjet/mach12-gh-issue-read/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 mach12:gh-issue-read

Your own site · 80×15
<a href="https://agentmods.dev/commands/leanandmean/scramjet/mach12-gh-issue-read"><img src="https://agentmods.dev/badge/commands/leanandmean/scramjet/mach12-gh-issue-read.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 913 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.00020 $0.00913
Opus 5.5 $0.00008 $0.00365
Sonnet 5.5 $0.00004 $0.00183
Haiku 4.5 $0.00002 $0.00091

Measured 27d ago against content hash 146140da862e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mach12:gh-issue-read 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 27d 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.

packages/scramjet/mach12/commands/mach12:gh-issue-read.md · 60 lines

How it starts

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

Read GitHub Issue

Goals

  • Return the caller an authoritative issue snapshot containing the parent metadata and complete chronological comment stream.
  • When requested, identify the most recent matching marker comment and its numeric ID without weakening completeness checks.
  • Make incomplete or malformed history explicit rather than presenting partial evidence as authoritative.

This subroutine is gh-specific. A future forge-agnostic command set would substitute an equivalent glab-issue-read (or similar); the marker-hunt logic stays the same.

Step 1: Parse input

Extract:

  • The issue number (required, first token).
  • An optional --marker <html-marker> flag naming an HTML comment marker to locate (e.g., --marker mach12-plan, --marker mach12-decisions).
  • An optional --repo <owner/repo> flag identifying a canonical public GitHub repository to read instead of the checkout repository. Accept only a validated owner/repo identity; reject malformed, non-canonical or inaccessible targets rather than falling back to the checkout.

If no issue number is present, return an error to the caller and stop.

Step 2: Read the issue and complete comment stream

When --repo is omitted, resolve the canonical owner/name with gh repo view --json nameWithOwner. When supplied, resolve gh repo view <owner/repo> --json nameWithOwner,url, require a canonical https://github.com/<owner>/<repo> URL and verify that the returned identity matches the requested owner/repo (GitHub identity comparison is case-insensitive). Use this resolved owner and name, never the checkout's defaults, for repository(owner:$owner,name:$name) in the gh api graphql --paginate query. Pass explicit variables for owner, name, issue number, and $endCursor. Request parent title, body, createdAt, updatedAt, and:

comments(first: 100, after: $endCursor) {
  totalCount
  nodes { databaseId body author { login } authorAssociation createdAt url }
  pageInfo { hasNextPage endCursor }
}

Read the full file on GitHub · 60 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. 27d ago Changed · +1 lines 146140da862e
  2. 1mo ago Changed · +4 lines d61d1a2bf69c
  3. 1mo ago First seen · 55 lines · 20 tokens per session scan A 29836852cc72

Subscribe to this mod's changes

mach12:gh-issue-read is a command published in the GitHub repository LeanAndMean/scramjet (8 stars, last pushed today), licensed Apache-2.0. It adds 20 tokens to every session and 913 once invoked, about $0.0001 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-08-31.