Borrowing it
Nothing to install: this file belongs to brayandiazc/project-starter-template-es-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/brayandiazc/project-starter-template-es-ai/main/.claude/skills/actualizar-plantilla/SKILL.mdgit clone --depth 1 https://github.com/brayandiazc/project-starter-template-es-aiWrote 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/brayandiazc/project-starter-template-es-ai/actualizar-plantilla)<a href="https://agentmods.dev/skills/brayandiazc/project-starter-template-es-ai/actualizar-plantilla"><img src="https://agentmods.dev/badge/skills/brayandiazc/project-starter-template-es-ai/actualizar-plantilla/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/brayandiazc/project-starter-template-es-ai/actualizar-plantilla"><img src="https://agentmods.dev/badge/skills/brayandiazc/project-starter-template-es-ai/actualizar-plantilla.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.00091 | $0.01578 |
| Opus 5 | $0.00046 | $0.00789 |
| Sonnet 5 | $0.00018 | $0.00316 |
| Haiku 4.5 | $0.00009 | $0.00158 |
Grade A, and why
actualizar-plantilla 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sincroniza el tooling de este proyecto con la versión actual de su plantilla de origen. Solo toca la capa reutilizable — nunca la documentación ya rellenada ni el código.
El workflow
.github/workflows/template-update-check.ymlrevisa semanalmente si la plantilla publicó mejoras y abre un issue de aviso — esta skill es la que las aplica.
Paso 1 — Leer el origen
Lee .template-origin en la raíz (lo escribe /instanciar):
repo=https://github.com/brayandiazc/project-starter-template-es-ai
commit=<sha-de-la-plantilla-al-instanciar>
fecha=YYYY-MM-DD
versiones=<versiones del CHANGELOG de la plantilla al instanciar, separadas por coma>
Si no existe, pregunta de qué plantilla/variante vino el proyecto y desde qué fecha aproximada, y usa el tag/commit de esa época como base.
Paso 2 — Calcular el diff del tooling
Clona la plantilla a un directorio temporal y calcula qué cambió desde el commit de origen, limitado a las rutas de tooling:
git clone --quiet <repo> /tmp/tpl-update && cd /tmp/tpl-update
git diff --stat <commit-origen>..HEAD -- \
.claude/ .github/scripts/ .github/workflows/ specs/_template/ \
docs/conventions/_template.md
Excluye siempre: README.md, docs/ rellenados, CHANGELOG.md, LICENSE y cualquier
archivo que el proyecto haya adaptado (compara antes de pisar; si el archivo local
difiere de la versión vieja de la plantilla, es una adaptación local — muéstrala y
pregunta).
Documentos: distingue NUEVO de EXISTENTE
«No tocar la documentación» es la regla correcta para los documentos que el proyecto ya
tiene rellenados. No lo es para los que no existen. Un proyecto que adoptó la
plantilla hace tiempo puede estar a dieciséis documentos de distancia —convenciones
nuevas, convenciones nuevas, la definición de terminado— y hoy no se los trae nadie: esta
skill los excluye por diseño y /instanciar cree que el proyecto es virgen.
# Documentos de la plantilla que el proyecto NO tiene: traerlos es seguro.
(cd /tmp/tpl-update && find docs legal design -type f -name "*.md" 2>/dev/null) \
| while IFS= read -r f; do [ -e "$f" ] || echo "NUEVO: $f"; done
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 Changed · +67 lines 86c5feddc7a6
- 11d ago First seen · 58 lines · 91 tokens per session scan A 9f42c25c5e3d
actualizar-plantilla is a skill published in the GitHub repository brayandiazc/project-starter-template-es-ai (15 stars, last pushed 4d ago), licensed MIT. It adds 91 tokens to every session and 1,578 once invoked, about $0.0005 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-01.
Other skills, from other repositories
cloudron-app-publishing
Distribute Cloudron apps via CloudronVersions.json version catalogs.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
fork-fleet
Fork divergence monitor - tracks where the fleet's active forks diverge in CODE (unique commits, new/modified skills) and CONFIG (enable/var/model/schedule vs upstream), gated on real change.
arbor-agent-executor
Executor-dispatch phase for Arbor. Use when implementing an Idea Tree node through RunExecutor or RunExecutorParallel semantics: isolated git worktree, executor prompt construction, eval metadata injection, RunTraining policy, smoke/full evaluation, report parsing, artifact persistence, tree update, and insight…
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.