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.
git clone --depth 1 https://github.com/luanpdd/kit-mcpWrote 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/commands/luanpdd/kit-mcp/publicar-rapido)<a href="https://agentmods.dev/commands/luanpdd/kit-mcp/publicar-rapido"><img src="https://agentmods.dev/badge/commands/luanpdd/kit-mcp/publicar-rapido/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/commands/luanpdd/kit-mcp/publicar-rapido"><img src="https://agentmods.dev/badge/commands/luanpdd/kit-mcp/publicar-rapido.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.00051 | $0.02220 |
| Opus 5 | $0.00026 | $0.01110 |
| Sonnet 5 | $0.00010 | $0.00444 |
| Haiku 4.5 | $0.00005 | $0.00222 |
Grade A, and why
publicar-rapido 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 5d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/publicar-rapido — Pipeline Notion + PR + Cofre, sem cerimônia de milestone
Variante de /publicar para mudanças que não passaram pelo fluxo completo de milestone: hotfix em produção, fix expresso (1 migration / 1 PR), refatoração curta, mudança trivial que precisa cross-link Notion + Obsidian + PR mesmo sem ROADMAP arquivado.
Quando usar
- Hotfix em produção: 1-3 commits, branch curta, sem milestone aberto.
- Pequena feature isolada que não justificou abrir milestone.
- Correção de bug urgente que precisa ir documentada mas o overhead do
/publicarnão compensa.
Não use quando o trabalho foi um milestone de várias fases — use /publicar (que valida MILESTONE-AUDIT.md, ROADMAP arquivado, etc).
Diferenças vs /publicar
| Aspecto | /publicar |
/publicar-rapido |
|---|---|---|
| Pré-requisitos de planejamento | ROADMAP + MILESTONE-AUDIT obrigatórios | Apenas commit(s) na branch |
| Detecção de versão | De STATE.md |
De package.json ou git tag mais recente |
| Detecção de tipo | Inferido do milestone | Inferido do commit message (fix:/feat:/refactor:/chore: prefix) |
| Notion | Página de changelog do milestone | Entrada curta na página de changelog com 1 parágrafo |
| Cofre Obsidian | Nota de PR + Changelog completo + componentes afetados | Apenas nota de PR + entrada no Changelog |
Pre-flight sync com main |
Sim (Passo 0) | Sim — herdado |
| Tempo médio | 60-90s | ~30s |
Processo
Passo 0 — Pre-flight: sincronizar com main (obrigatório, herdado de /publicar)
Igual ao Passo 0 do /publicar: git fetch origin main, lista commits novos, oferece rebase/merge/ignorar/cancelar via AskUserQuestion. Não pule — esse é exatamente o cenário onde dev paralelo causa conflito tardio em hotfix.
Passo 1 — Detectar contexto
1.1 — Tipo do commit
Leia o commit mais recente (git log -1 --format=%B). Se houver múltiplos commits desde origin/main, leia todos (git log origin/main..HEAD --format=%B).
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.
- 5d ago First seen · 208 lines · 51 tokens per session scan A e666c7546187
publicar-rapido is a command published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 2,220 once invoked, about $0.0003 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-09-03.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.
weekly-summary
Generate weekly work summary from git activity.
next
Suggest the most likely next workflow action based on current context.
update-check.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.