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-publishgit 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-publish)<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/github-publish"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/github-publish/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-publish"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/github-publish.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.00086 | $0.01259 |
| Opus 5.5 | $0.00034 | $0.00504 |
| Sonnet 5.5 | $0.00017 | $0.00252 |
| Haiku 4.5 | $0.00009 | $0.00126 |
Grade A, and why
github-publish 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmap → GitHub
Nada é escrito no GitHub antes do dry-run e de um "sim" explícito.
GHP="<plugin-root>/scripts/ghp.py" · contrato do roadmap em
<plugin-root>/references/roadmap-contract.md.
1. Entrada
os argumentos = caminho do roadmap.json. Leia o arquivo: schema deve ser
pwdev-roadmap/1. Se o roadmap vier do pwdev-prd, ele já passou pelo roadmap-check.py e
pelo gate de aprovação — não repita.
2. Destino
De .planning/github.json: repo, owner, project.number, project.spec.
- Sem config → siga a skill
github-initprimeiro. - Sem Project → ofereça:
1. Criar agora (skill github-project)·2. Escolher um existente.
3. Mapeamento e opções
Apresente o padrão e pergunte se quer mudar (uma pergunta):
Como publicar o roadmap "{título}" ({F} features, {T} tasks, {E} dependências)?
1. Padrão — Fase=Milestone · Épico=issue · Feature=sub-issue do épico · Tasks=checklist na feature
2. Tasks viram issues — como o padrão, e cada Task vira sub-issue da feature
3. Enxuto — só Features viram issues (fase e épico ficam no corpo e nos campos)
Histórias de usuário ({S}, {R} ready): no corpo da feature [padrão] · como sub-issues da feature
Extras: labels (type:*, priority:*, prd:<slug>) [sim] · milestones por fase [sim]
Mapeamento → --mapping default | task-issues | flat; histórias → --stories body | issues
(a linha de histórias só aparece se o roadmap tiver stories); extras desligados →
--no-labels / --no-milestones. No corpo, cada história leva a frase "Como…, quero…, para…",
os CA como checklist (Gherkin em bloco) e as RN com regra e exemplo; como sub-issue, a história
ganha label type:story (e status:draft enquanto não estiver ready), Tipo=História no Project
e "blocked by" entre histórias conforme depends_on.
4. Dry-run (obrigatório)
python3 "$GHP" publish --roadmap "<roadmap.json>" --owner "<owner>" --repo "<repo>" \
--number <n> --mapping <m> --stories <body|issues> [--no-labels] [--no-milestones] --dry-run
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 · 93 lines · 86 tokens per session scan A 46dabd3404b8
github-publish 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 86 tokens to every session and 1,259 once invoked, about $0.0003 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
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…