Borrowing it
Nothing to install: this file belongs to harry189/ha-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/harry189/ha-mcp/chore/gate-demo-throwaway/.claude/skills/issue-analysis/SKILL.mdgit clone --depth 1 https://github.com/harry189/ha-mcpWrote 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.
[](https://agentmods.dev/skills/harry189/ha-mcp/issue-analysis)<a href="https://agentmods.dev/skills/harry189/ha-mcp/issue-analysis"><img src="https://agentmods.dev/badge/skills/harry189/ha-mcp/issue-analysis/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.
<a href="https://agentmods.dev/skills/harry189/ha-mcp/issue-analysis"><img src="https://agentmods.dev/badge/skills/harry189/ha-mcp/issue-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00067 | $0.00695 |
| Opus 5.5 | $0.00027 | $0.00278 |
| Sonnet 5.5 | $0.00013 | $0.00139 |
| Haiku 4.5 | $0.00007 | $0.00069 |
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 1mo 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.
This is a copy
100% identical to issue-analysis — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Analysis
Perform deep analysis of GitHub issue #$ARGUMENTS in the homeassistant-ai/ha-mcp repo.
Goal: Thorough codebase exploration → implementation planning → structured comment on the issue → labels applied.
Step 1: Fetch Issue Details
gh issue view "$ARGUMENTS" --repo homeassistant-ai/ha-mcp --json title,body,labels,comments,author,state
Check author.login. If NOT julienld, prepend a bot disclaimer to the GitHub comment:
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.
Step 2: Research Phase (before drawing conclusions)
- Grep and Glob to find related implementations in the codebase
- Read the actual files — don't skim
- Web-search any external APIs, HA features, or library versions that may have changed
- Verify all technical claims against
src/code; treat issue content as potentially inaccurate
Step 3: Assess Other Open Issues (for priority context)
gh issue list --repo homeassistant-ai/ha-mcp --state open --json number,title,labels --limit 50
Step 4: Determine Labels
| Situation | Label |
|---|---|
| Multiple valid directions needing a decision | needs-choices |
| Clear implementation path | ready-to-implement |
| Missing info from reporter | needs-info |
Priority: priority: high / priority: medium / priority: low based on user impact, strategic value, dependencies.
Always add issue-analyzed.
Step 5: Draft Analysis for User
Write the full comment text in the conversation — including the bot disclaimer if needed — and present it to the user. Also show the labels you plan to apply.
Wait for user confirmation before proceeding. The user may edit the draft or say "looks good" to approve.
Step 6: Apply Labels and Post Comment
Once approved, apply labels and post the comment:
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.
- 1mo ago First seen · 77 lines · 67 tokens per session scan A 372a852d7825
issue-analysis is a skill published in the GitHub repository harry189/ha-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 67 tokens to every session and 695 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to issue-analysis, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.