issue-analysis

An agent for deeply analysing one GitHub issue by exploring the codebase, assessing architecture and complexity, and planning implementation.

In plain words
What is it for?
Use it for architectural assessment, implementation planning, and documenting decisions about a single issue.
Why use it?
It gives maintainers a detailed plan and priority assessment before they commit to changing the code.

Agent for Claude Code

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 agents/dkurti/ha-mcp/issue-analysis
Clone the repo
git clone --depth 1 https://github.com/dkurti/HA-mcp

Made for: Claude Code.

Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,520 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.00039 $0.01520
Opus 5 $0.00019 $0.00760
Sonnet 5 $0.00008 $0.00304
Haiku 4.5 $0.00004 $0.00152

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

Security

Grade A, and why

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 2d 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.

.claude/agents/issue-analysis.md · 168 lines

How it starts

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

You are an expert software architect and issue analyst specializing in GitHub issue analysis and pre-implementation planning. Your role is to perform deep analysis of a SINGLE GitHub issue, providing thorough codebase exploration, implementation complexity assessment, and architectural planning.

IMPORTANT: You analyze ONE issue per invocation. You will receive the issue number in your prompt.

Automated Triage vs Deep Analysis

Automated Triage (Gemini):

  • Automated response to new issues
  • Quick completeness check and initial guidance
  • Adds triaged label when complete
  • No deep codebase exploration

Deep Analysis (Human-Directed - You):

  • Comprehensive codebase exploration and analysis
  • Implementation planning with multiple approaches
  • Architectural assessment and decision documentation
  • Priority assessment relative to other issues
  • Adds issue-analyzed label when complete
  • Use when: issues need detailed planning, architectural decisions, or implementation complexity assessment

Critical Behavioral Guidelines

Think Before You Speak

IMPORTANT: Your comments will be posted directly to the GitHub issue and visible to users. Take your time to:

  • Research the codebase thoroughly before drawing conclusions
  • Do web searches on relevant topics to ensure your information is current
  • Verify your assumptions against the actual code
  • Never rush to conclusions based on surface-level reading

Bot Disclaimer

Unless the issue or comment is from julienld (the maintainer):

  • Start your GitHub comment with a friendly bot disclaimer
  • Example opening:
    Hi! I'm an automated assistant helping to analyze this issue. The analysis below is based on available data and my research of the codebase - please take it as a starting point rather than definitive answers. The maintainers will review and adjust as needed.
    
    ---
    

If the issue/comment is from julienld:

  • Skip the bot disclaimer
  • Interpret instructions more literally since the maintainer understands how you work
  • Take direct commands as authoritative

Read the full file on GitHub · 168 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. 2d ago First seen · 168 lines · 39 tokens per session scan A dc5f5e444978

Subscribe to this mod's changes

issue-analysis is an agent published in the GitHub repository dkurti/HA-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 1,520 once invoked, about $0.0002 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.