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 skills add pwdev-solucoes/pwdev-claude-marketplace --skill github-issuesgit clone --depth 1 https://github.com/pwdev-solucoes/pwdev-claude-marketplaceWrote 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/pwdev-solucoes/pwdev-claude-marketplace/github-issues)<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/github-issues"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/github-issues/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/pwdev-solucoes/pwdev-claude-marketplace/github-issues"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/github-issues.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.00170 | $0.01488 |
| Opus 5.5 | $0.00068 | $0.00595 |
| Sonnet 5.5 | $0.00034 | $0.00298 |
| Haiku 4.5 | $0.00017 | $0.00149 |
Grade A, and why
github-issues 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 27d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issues e tarefas de Project
Você opera issues e itens de GitHub Projects pelo gh CLI, e pelo ghp.py onde o gh não
cobre (sub-issues, blocked-by, campos do Project por nome). Receitas exatas:
gh-recipes — leia a seção da intenção antes de executar.
GHP="<plugin-root>/scripts/ghp.py"
Contexto
- Repo e Project padrão:
.planning/github.json(repo,owner,project.number). Sem ele, use o repo do diretório (gh repo view) e pergunte o Project só se a intenção precisar. - Issues publicadas de um roadmap:
.planning/github/<slug>.map.jsontraduz IDs do roadmap (F01-E02-FT01) em números (#14) — aceite os dois. - Pré-requisitos:
gh auth statusok; operações de Project exigem o scopeproject(! gh auth refresh -s project).
Mapa de intenção
| Intenção | Como |
|---|---|
| Criar issue | gh issue create --repo R --title --body-file --label --assignee --milestone; opcional: adicionar ao Project e setar Status |
| Ver / listar | gh issue view N --json ... · gh issue list --search "..." |
| Editar | gh issue edit N (--title, --body-file, --add-label/--remove-label, --add-assignee, --milestone) |
| Comentar | gh issue comment N --body-file |
| Fechar | gh issue close N --reason completed|"not planned" --comment "..." |
| Reabrir | gh issue reopen N --comment "..." |
| Sub-issue | ghp.py link sub|unsub --repo R --parent P --child C |
| Dependência | ghp.py link block|unblock --repo R --issue N --blocker M (N fica bloqueada por M) |
| O que bloqueia / o que é bloqueado | ghp.py deps --repo R --issue N |
| Mover no Project / editar campo | ghp.py item set --owner O --number P --url URL --field Status --value "Em andamento" |
| Adicionar ao Project | gh project item-add P --owner O --url URL |
| Arquivar item | gh project item-archive P --owner O --id ITEM |
| Marcar task do checklist | editar o corpo da feature trocando - [ ] T0n por - [x] T0n |
| Marcar critério de aceite atendido | editar o corpo (feature, ou sub-issue da história) trocando - [ ] **CA-0n por - [x] **CA-0n da história US-xx citada; fechar a história só quando todos os CA estiverem marcados |
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.
- 27d ago First seen · 84 lines · 170 tokens per session scan A 11381707eacb
github-issues is a skill published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (3 stars, last pushed 10d ago), licensed Apache-2.0. It adds 170 tokens to every session and 1,488 once invoked, about $0.0007 per session on Opus 5.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-09-28.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…