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)<a href="https://agentmods.dev/commands/luanpdd/kit-mcp/publicar"><img src="https://agentmods.dev/badge/commands/luanpdd/kit-mcp/publicar.svg" alt="Measured on agentmods" 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.00026 | $0.05349 |
| Opus 5 | $0.00013 | $0.02674 |
| Sonnet 5 | $0.00005 | $0.01070 |
| Haiku 4.5 | $0.00003 | $0.00535 |
Grade A, and why
publicar 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 4d 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 — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/publicar — Publicar Milestone com Documentação Notion + GitHub
Publica o milestone atual: cria documentação no Notion, abre PR no GitHub e inclui o link Notion na descrição do PR.
Quando usar
Após concluir e arquivar um milestone com /concluir-marco.
Heurística de gatilho (importante): quando o usuário diz "publicar" depois de aplicar mudanças de código (commits novos, migration aplicada, branch atual com diff vs main), interprete como pipeline completo — não apenas git push. Faça Notion + PR + Obsidian. Para push isolado em outra branch sem cerimônia, o usuário deve pedir explicitamente "só fazer push" ou usar git push ele mesmo. Para fix expresso sem milestone, use /publicar-rapido (variante leve sem dependência de ROADMAP/MILESTONE-AUDIT).
Dependências obrigatórias
.claude/notion-config.jsonpresente e preenchido — fluxo de fallback novo (1.4): se ausente, NÃO encerre. Em vez disso, vá para o Passo 0.5 (auto-detect Notion) abaixo: tente buscar a página do projeto via Notion MCPnotion-searchno workspace e ofereça gerar o config automaticamente. Encerrar é fallback de último recurso.- Notion MCP configurado na sessão Claude Code
ghCLI autenticado (gh auth status)- Milestone arquivado com
/concluir-marco
Dependências opcionais
$OBSIDIAN_TEAM_VAULT— caminho absoluto do cofre Obsidian do time (sincronizado via Git).- Fallback novo (1.4): se ausente, antes de pular o Passo 5, o Passo 0.7 (auto-detect Obsidian) tenta caminhos canônicos (
~/Documentos/Obsidian/chat-trynux/,~/Documents/Obsidian/chat-trynux/, e variantes Windows). Só se nenhum bater é que o Passo 5 é pulado com aviso.
- Fallback novo (1.4): se ausente, antes de pular o Passo 5, o Passo 0.7 (auto-detect Obsidian) tenta caminhos canônicos (
Processo
Passo 0 — Pre-flight: sincronizar com main ⚠️ NOVO 1.4
Por que isso existe: vários devs trabalhando no mesmo projeto significa que origin/main pode ter avançado desde sua última sincronização. Antes de abrir PR, descubra se há trabalho novo e dê ao dev a chance de integrar (evita conflitos grandes mais tarde).
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.
- 4d ago First seen · 500 lines · 26 tokens per session scan A 61f0121406d6
publicar is a command published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 5,349 once invoked, about $0.0001 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.