claude-desktop-extra: Skill for Claude Code

.claude/skills/check-issue/SKILL.md

check-issue is a skill for Claude Code from patrickjaja/claude-desktop-extra. It costs 97 tokens per session (4,307 once invoked), scanned B, original, MIT.

A workflow for taking GitHub bug reports from initial review through a fix, testing, release, and reporter follow-up. GitHub is a service for hosting code and tracking issues, which are written reports of bugs or requested changes.

In plain words
What is it for?
Use it to inspect issue reports, reproduce problems without changing a user's running app, coordinate implementation and review, run live checks, publish a release, and close the issue.
Why use it?
It gives a structured path for deciding whether a report belongs to the project, reproducing it safely, and checking the fix before release. It also requires approval at key steps such as writing the specification, committing, releasing, and commenting publicly.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: reads .claude/ paths; mentions subagents; names the AskUserQuestion tool.

This is patrickjaja/claude-desktop-extra's own configuration. It tells Claude Code how to work on claude-desktop-extra itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-desktop-extra configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 scripts/check-upstream-absorbed.py tmp/app.asar.contents tmp/extract/usr/lib/claude-desktop/resources/ion-dist.asar.

Reuse

Borrowing it

Nothing to install: this file belongs to patrickjaja/claude-desktop-extra. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/patrickjaja/claude-desktop-extra/master/.claude/skills/check-issue/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/patrickjaja/claude-desktop-extra

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/patrickjaja/claude-desktop-extra/check-issue/github.svg)](https://agentmods.dev/skills/patrickjaja/claude-desktop-extra/check-issue)
Your own site
<a href="https://agentmods.dev/skills/patrickjaja/claude-desktop-extra/check-issue"><img src="https://agentmods.dev/badge/skills/patrickjaja/claude-desktop-extra/check-issue/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 check-issue

Your own site · 80×15
<a href="https://agentmods.dev/skills/patrickjaja/claude-desktop-extra/check-issue"><img src="https://agentmods.dev/badge/skills/patrickjaja/claude-desktop-extra/check-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,307 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 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.00097 $0.04307
Opus 5.5 $0.00039 $0.01723
Sonnet 5.5 $0.00019 $0.00861
Haiku 4.5 $0.00010 $0.00431

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

Security

Grade B, and why

check-issue scanned grade B with 2 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 3d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

- Build only when the maintainer asks; they install (`sudo pacman -U ...`). Check that the running app started after the install before testing.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

**Verify before presenting.** Spot-check a worker's key upstream claim in the pristine bundle yourself before calling it the root cause; the maintainer will ask whether it was audited, and whether there is an event to ho
.claude/skills/check-issue/SKILL.md · 177 lines

How it starts

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

Check issue - from bug report to shipped fix

Issues: $ARGUMENTS

Open issues right now: !gh -R patrickjaja/claude-desktop-extra issue list --state open --limit 10 2>/dev/null || echo "(gh not ready)" Latest release: !gh -R patrickjaja/claude-desktop-extra release list --limit 1 2>/dev/null || echo "(gh not ready)" Upstream version patches target: !cat .upstream-version 2>/dev/null

The main thread orchestrates. Investigation, implementation, review and live tests run in dispatched workers. Follow the global subagent tier rules: name the tier and the reason in every dispatch.

Gates. Ask before each of these, and treat each approval as covering only its own step:

  • the spec
  • building or installing (the maintainer does this themselves)
  • commit and push
  • the release
  • every public issue comment

Phase 1 - read everything

for n in <numbers>; do gh issue view $n --json title,author,createdAt,body; gh issue view $n --comments; done
  • --comments shows only the comments, never the body. Always fetch the body separately with --json body.
  • Pull any --diagnose gist the reporter linked with gh gist view <id> --raw > <scratch>/gist<n>/diagnose.txt. Then grep it for session type, compositor, scale, bridges and versions.
  • Compare the reporter's version with .upstream-version and the installed package (pacman -Q claude-desktop-extra). If the extract in tmp/ matches the upstream version the reports are against, it can be reused read-only.

Phase 2 - investigate in parallel (read-only)

Dispatch one worker per issue. A contained parsing or logic bug goes to sonnet. Coordinate math, renderer lifecycle, or minified-anchor work goes to opus.

Each brief carries:

  • the issue text and the suspected file:line
  • "READ-ONLY, no edits, no commits"
  • a scratch dir per issue
  • this question: ours or upstream?

Ours or upstream:

  • Computer Use (js/cu_*, the bridges) is always ours, because upstream ships no Linux CU.
  • For anything else:
    • Find upstream's code in the pristine bundle (grep -a across tmp/app.asar.contents/.vite/build/index*.js).
    • Confirm that our patches do not touch that path.
    • Search anthropics/claude-code issues for the same symptom.
  • An upstream bug that only breaks on Linux is still ours to patch. It counts as a functional gap, not a cosmetic one.

Read the full file on GitHub · 177 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. 3d ago Changed · +13 lines cdf7eca28bd0
  2. 9d ago Changed · +3 lines scan A → B acb1928b4bb6
  3. 10d ago First seen · 161 lines · 97 tokens per session scan A 10efffd03e30

Subscribe to this mod's changes

check-issue is a skill published in the GitHub repository patrickjaja/claude-desktop-extra (726 stars, last pushed yesterday), licensed MIT. It adds 97 tokens to every session and 4,307 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-27.

Related

check-issue compared with skills from other repositories

check-issue next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
check-issuepatrickjaja/claude-desktop-extraSkill726yesterdayMITB97Claude Code
changelog-generatorcomposio-community/awesome-claude-pluginsSkill2.0kyesterdaynoneA48Claude Code
perf-theory-gatherercomposio-community/awesome-claude-pluginsSkill2.0kyesterdaynoneA20Claude Code
version-bumpthedotmack/claude-memSkill114kyesterdayApache-2.0A64Claude Code
batchasgeirtj/system_prompts_leaksSkill71k2d agoCC0-1.0A30Claude Code
git-advanced-workflowswshobson/agentsSkill42kyesterdayMITA54Claude Code
agent-merge-conflict-arbiterNousResearch/hermes-agentSkill261kyesterdayMITA19Claude Code, Codex