tackle-issue

tackle-issue is a skill for Claude Code, Codex from gtapps/claude-code-hermit. It costs 149 tokens per session (2,491 once invoked), scanned A, original, MIT.

A read-only investigation tool for deciding whether a GitHub issue or proposed change is worth doing. A monorepo is one repository containing multiple related projects, and this tool is designed for that setup.

In plain words
What is it for?
Use it to triage issue numbers, inspect pasted proposals, challenge assumptions, and decide whether to proceed with the work.
Why use it?
It checks whether the reported problem is real, already fixed, badly framed, or larger than necessary before implementation begins. This helps avoid blindly implementing an inaccurate or oversized request.

Skill for Claude CodeCodex

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 skills/gtapps/claude-code-hermit/tackle-issue
Any agent
npx skills add gtapps/claude-code-hermit --skill tackle-issue
Clone the repo
git clone --depth 1 https://github.com/gtapps/claude-code-hermit

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 tackle-issue

README.md
[![agentmods](https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/tackle-issue.svg)](https://agentmods.dev/skills/gtapps/claude-code-hermit/tackle-issue)
Your own site
<a href="https://agentmods.dev/skills/gtapps/claude-code-hermit/tackle-issue"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/tackle-issue.svg" alt="Measured on agentmods" height="20"></a>
Per session 149 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,491 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.00149 $0.02491
Opus 5 $0.00075 $0.01246
Sonnet 5 $0.00030 $0.00498
Haiku 4.5 $0.00015 $0.00249

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

Security

Grade A, and why

tackle-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 today.

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.

.agents/skills/tackle-issue/SKILL.md · 206 lines

How it starts

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

Tackle Issue

Triage first, then optionally set up the work. Read-only until the operator picks "go" at the end. Implementation, commit, and PR happen outside this skill.

Mindset

An issue or proposal is a hypothesis, not a spec. Most issues here are filed by AI agents (hermit-scribe): intent is usually right, framing often is not (stale paths, first-idea fix, oversized scope, premise already fixed, or no bug at all). Falsify the premise before planning anything. If it survives, judge separately whether the change is worth its cost.

Two failure modes, both disqualifying:

  • Rubber-stamping: implementing exactly what was written when a simpler fix exists or the premise is partly wrong.
  • Reflex-pushback: manufactured objections. If the premise holds and ROI is good, say "ship as written" plainly.

Proportionality: scale investigation to blast radius. A one-file doc fix needs falsification steps 1 and 3 only, and a two-line trade-off note. Anything touching hooks, shipped skills, or release machinery gets the full pass, including a live probe when a harness-behavior claim is load-bearing.

Dispatch

  • Issue number ("tackle issue 99", "#42", "owner/repo#N"): gh issue view <N> --repo <owner/repo from input, default gtapps/claude-code-hermit> --json title,body,labels,comments,author,state,url Read the comments: they often say "already fixed" or change scope, and they override the body. Pull referenced issues/PRs when the body leans on them. Closed issue → surface that and ask before continuing. Also run gh pr list --repo <repo> --state open --search "<N>": an open PR already covering the issue usually means DEFER to that PR.
  • Pasted content (proposal, spec, free-form): treat the text as the task body. Triage output only, no handoff.
  • Picker ("tackle the next issue", "what should I work on", bare /tackle-issue): run Picker below, then continue as issue-number mode.
  • Ambiguous ("tackle this", no number, no paste): ask which mode before fetching anything.
  • --investigate-only (combines with issue-number mode): full triage report including the plan sections on positive verdicts, then stop. No branch, no tasks.

Read the full file on GitHub · 206 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. today Changed f2377d85c7f2
  2. 4d ago First seen · 206 lines · 149 tokens per session scan A 63026c6a6790

Subscribe to this mod's changes

tackle-issue is a skill published in the GitHub repository gtapps/claude-code-hermit (73 stars, last pushed today), licensed MIT. It adds 149 tokens to every session and 2,491 once invoked, about $0.0007 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.