Borrowing it
Nothing to install: this file belongs to jpawlowski/hacs.integration_blueprint. 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/jpawlowski/hacs.integration_blueprint/main/.agents/skills/ha-issue-triage/SKILL.mdgit clone --depth 1 https://github.com/jpawlowski/hacs.integration_blueprintWrote 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/jpawlowski/hacs.integration_blueprint/ha-issue-triage)<a href="https://agentmods.dev/skills/jpawlowski/hacs.integration_blueprint/ha-issue-triage"><img src="https://agentmods.dev/badge/skills/jpawlowski/hacs.integration_blueprint/ha-issue-triage/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/jpawlowski/hacs.integration_blueprint/ha-issue-triage"><img src="https://agentmods.dev/badge/skills/jpawlowski/hacs.integration_blueprint/ha-issue-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00221 | $0.03214 |
| Opus 5 | $0.00111 | $0.01607 |
| Sonnet 5 | $0.00044 | $0.00643 |
| Haiku 4.5 | $0.00022 | $0.00321 |
Grade A, and why
ha-issue-triage 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue triage and branch/PR-based fixing
A backlog-scale companion to the ad-hoc flow in AGENTS.md. That flow (commit directly, on explicit request, no
push) is still correct for a single request handled live with the developer watching. This skill is for the
different situation: working through several issues in a row, where a branch + pull request + green CI is the
review surface, because nobody is watching each individual commit in real time. Both are legitimate; pick based on
whether you're handling one request or a backlog, not out of habit.
Merge autonomy — read this before the fix flow below
By default, ask for explicit confirmation before merging any pull request this flow opens — merging is a
shared-state, hard-to-reverse action (AGENTS.md, "Executing actions with care"), and a backlog run touches several
of them in a row.
Skip that per-PR confirmation, and merge automatically on green CI, only when this session was entered through a
dedicated entry point built for full autonomy — a command that exists specifically to invoke this flow (such as
/issues, if your client offers slash commands), or an explicit instruction scoped to the session ("auto-merge
these", "don't ask me each time today"). Ad-hoc conversational use of this skill — "hey, can you triage my issues" —
always asks. State which mode you're in once, at the start of a run, rather than leaving it implicit.
Concurrency: running more than one instance on the same repo
If nothing else is touching this backlog concurrently, skip this section — claim/release below are harmless no-ops. It exists for when you might be one of several agent sessions working the same repo at once.
Instance ID: generate one ID of the form <epoch>-<rand> (`date +%s` seconds, plus a random suffix) at the
start of a run, show it, and reuse the literal value in every later command — shell variables do not survive
between separate tool calls. The lock label is wip:<id>; the epoch doubles as its creation timestamp for the TTL
below.
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.
- 11d ago First seen · 193 lines · 221 tokens per session scan A d7391d5b8ec2
ha-issue-triage is a skill published in the GitHub repository jpawlowski/hacs.integration_blueprint (49 stars, last pushed 4d ago), licensed MIT. It adds 221 tokens to every session and 3,214 once invoked, about $0.0011 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.
Other skills, from other repositories
homeassistant
Source-layer Home Assistant guide material preserved behind the runtime guide.
bat-story-eval
Compare MCP tool behavior between target and baseline versions using pre-built and custom stories with diff-based triage.
contrib-pr-review
Review a contribution PR for safety, quality, and readiness. Checks for security concerns, test coverage, size appropriateness, and intent alignment. Use when reviewing external contributions.
issue-to-pr-resolver
Implement a GitHub issue end-to-end — create a worktree branch, implement the feature with tests, create a draft PR, then iteratively resolve all CI failures and review comments until the PR is clean. Use when you need to fully implement a GitHub issue from start to merge-ready. Triggers on "implement issue", "resolve…
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…