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/reaplicar-patches)<a href="https://agentmods.dev/commands/luanpdd/kit-mcp/reaplicar-patches"><img src="https://agentmods.dev/badge/commands/luanpdd/kit-mcp/reaplicar-patches/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/reaplicar-patches"><img src="https://agentmods.dev/badge/commands/luanpdd/kit-mcp/reaplicar-patches.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.00017 | $0.01054 |
| Opus 5 | $0.00009 | $0.00527 |
| Sonnet 5 | $0.00003 | $0.00211 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade A, and why
reaplicar-patches 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 6d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Passo 1: Detectar patches com backup
Verificar diretório de patches locais:
# Instalação global — detectar diretório de config do runtime
if [ -d "$HOME/.config/opencode/local-patches" ]; then
PATCHES_DIR="$HOME/.config/opencode/local-patches"
elif [ -d "$HOME/.opencode/local-patches" ]; then
PATCHES_DIR="$HOME/.opencode/local-patches"
elif [ -d "$HOME/.gemini/local-patches" ]; then
PATCHES_DIR="$HOME/.gemini/local-patches"
else
PATCHES_DIR="./.claude/local-patches"
fi
# Fallback para instalação local — verificar todos os diretórios de runtime
if [ ! -d "$PATCHES_DIR" ]; then
for dir in .config/opencode .opencode .gemini .claude; do
if [ -d "./$dir/local-patches" ]; then
PATCHES_DIR="./$dir/local-patches"
break
fi
done
fi
Ler backup-meta.json do diretório de patches.
Se nenhum patch encontrado:
Nenhum patch local encontrado. Nada a reaplicar.
Patches locais são salvos automaticamente quando você executa /atualizar
após modificar qualquer workflow, comando ou arquivo de agente do framework.
Sair.
Passo 2: Mostrar resumo de patches
## Patches Locais para Reaplicar
**Backup de:** v{from_version}
**Versão atual:** {ler arquivo VERSION}
**Arquivos modificados:** {contagem}
| # | Arquivo | Status |
|---|---------|--------|
| 1 | {file_path} | Pendente |
| 2 | {file_path} | Pendente |
Passo 3: Mesclar cada arquivo
Para cada arquivo em backup-meta.json:
-
Ler a versão com backup (cópia modificada pelo usuário de
local-patches/) -
Ler a versão recém-instalada (arquivo atual após atualização)
-
Comparar e mesclar:
- Se o novo arquivo for idêntico ao arquivo com backup: pular (modificação foi incorporada upstream)
- Se o novo arquivo diferir: identificar as modificações do usuário e aplicá-las à nova versão
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.
- 6d ago First seen · 125 lines · 17 tokens per session scan A 22b95891eaf3
reaplicar-patches is a command published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 1,054 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
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
handoff
Export a Waybill Bundle by default, or import one when requested.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.