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/dapi/claude-code-marketplace/github-issuesnpx skills add dapi/claude-code-marketplace --skill github-issuesgit clone --depth 1 https://github.com/dapi/claude-code-marketplaceWhat 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.00306 | $0.02614 |
| Opus 5 | $0.00153 | $0.01307 |
| Sonnet 5 | $0.00061 | $0.00523 |
| Haiku 4.5 | $0.00031 | $0.00261 |
Grade A, and why
github-issues scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -O "$url" How it starts
The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issues Management Skill
Управление GitHub issues через gh CLI с поддержкой sub-issues и атомарных операций над checkboxes.
КРИТИЧЕСКИЕ ПРАВИЛА
1. ВСЕГДА использовать gh, НИКОГДА WebFetch
# ПРАВИЛЬНО
gh issue view 123 -R owner/repo
# НЕПРАВИЛЬНО - НЕ ДЕЛАЙ ТАК!
# WebFetch для github.com/.../issues/...
2. Переименование вкладки zellij при начале работы с issue
Когда пользователь начинает работу с issue (читает issue, изучает задачу, обсуждает реализацию), переименуй вкладку zellij:
zellij-rename-tab-to-issue-number <ISSUE_NUMBER>
Скрипт безопасен: если мы не внутри zellij -- ничего не произойдёт.
Когда вызывать:
- Пользователь просит прочитать/показать issue
- Пользователь начинает обсуждать задачу из issue
- Первое обращение к issue в сессии
Когда НЕ вызывать:
- Отметка checkbox (мелкая операция)
- Закрытие/открытие issue
- Работа с labels
3. Атомарные операции с checkboxes (без кеша!)
ВАЖНО: При отметке checkbox ВСЕГДА выполняй атомарную операцию fetch→modify→push в ОДНОЙ команде. Это предотвращает конфликты при параллельной работе нескольких агентов.
# Атомарная отметка checkbox (fetch → modify → push) — ОДНОЙ СТРОКОЙ!
gh issue view 123 -R owner/repo --json body -q .body | sed 's/- \[ \] Точный текст пункта/- [x] Точный текст пункта/' | gh issue edit 123 -R owner/repo --body-file -
ВАЖНО: Команда должна быть в ОДНУ строку без \ переносов — иначе ошибка в zsh.
НИКОГДА не кешируй body issue! Всегда скачивай заново перед изменением.
4. Сначала отметить — потом продолжать
После выполнения любого пункта/этапа/шага:
- СНАЧАЛА отметить как выполненный в issue
- ПОТОМ переходить к следующему
Проверка зависимостей
При первом использовании проверь установленные расширения:
gh extension list
Если расширения отсутствуют — предложи установить:
# Для работы с sub-issues
gh extension install yahsan2/gh-sub-issue
# Для расширенного project management (опционально)
gh extension install rubrical-studios/gh-pmu
What ships with it
1 file 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.
- yesterday First seen · 272 lines · 306 tokens per session scan A 3f0c002370b7
github-issues is a skill published in the GitHub repository dapi/claude-code-marketplace (16 stars, last pushed 4mo ago), licensed MIT. It adds 306 tokens to every session and 2,614 once invoked, about $0.0015 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…