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.
npx agentmods add skills/jerry0022/dotclaude/setup-issuenpx skills add Jerry0022/dotclaude --skill setup-issuegit clone --depth 1 https://github.com/Jerry0022/dotclaudeWhat 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 | $0.00106 | $0.01799 |
| Opus 5 | $0.00053 | $0.00899 |
| Sonnet 5 | $0.00021 | $0.00360 |
| Haiku 4.5 | $0.00011 | $0.00180 |
Grade A, and why
setup-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 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.
How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Issue — GitHub Issue & Milestone Management
Create issues and milestones with enforced formatting and optional board integration.
Step 0 — Load Extensions
Check for optional overrides. Use Glob to verify each path exists before reading. Do NOT call Read on files that may not exist — skip missing files silently (no output).
- Global:
~/.claude/skills/setup-issue/SKILL.md+reference.md - Project:
{project}/.claude/skills/setup-issue/SKILL.md+reference.md - Merge: project > global > plugin defaults
Project extensions define:
- GitHub owner and project board ID
- Additional required labels (e.g.,
role:*,module:*) - GraphQL field IDs for board status/custom fields
- Milestone naming preferences
Step 1 — Gather details
Determine from user input or ask via AskUserQuestion:
- Title: Must follow
[TYPE] Short imperative descriptionformat - Type: bug, feature, refactor, chore, design, docs
- Description: Imperative mood, sentence case, no trailing period
- Target repo (
{target_repo}): anowner/nameslug when the issue belongs to a different repository than the session's. Absent → the current repo.
If project extension defines additional required fields (roles, modules), ask for those too.
Target repo — when a caller hands one over
Callers route issues to other repositories: /claude-learn files a plugin
defect against the plugin source repo from inside a consumer project, and files
a cross-project learning against that project. An issue silently created in
the wrong repo is worse than none — it looks successful, returns a valid URL,
and leaves the real repo untouched.
- Carry
{target_repo}through to Step 2 as--repo, to Step 3's skip condition, and to Step 4's check. - Labels, milestones, and board fields configured for the current project do
not necessarily exist in
{target_repo}. Verify withgh label list --repo {target_repo}before sending any label — includingtype:*:gh issue createhard-fails on an unknown label, and a target repo that never adopted thetype:scheme would reject every issue. Missing there → create the issue without it and say so, rather than losing the issue. Drop milestone/board steps unless the target is configured for them.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 160 lines · 106 tokens per session scan A a0d013723b22
setup-issue is a skill published in the GitHub repository Jerry0022/dotclaude (4 stars, last pushed 2d ago), licensed MIT. It adds 106 tokens to every session and 1,799 once invoked, about $0.0005 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…