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 Mazalucas/El-DT-Lightweight-Army --skill git-actualizargit clone --depth 1 https://github.com/Mazalucas/El-DT-Lightweight-ArmyWrote 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/mazalucas/el-dt-lightweight-army/git-actualizar)<a href="https://agentmods.dev/skills/mazalucas/el-dt-lightweight-army/git-actualizar"><img src="https://agentmods.dev/badge/skills/mazalucas/el-dt-lightweight-army/git-actualizar/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/mazalucas/el-dt-lightweight-army/git-actualizar"><img src="https://agentmods.dev/badge/skills/mazalucas/el-dt-lightweight-army/git-actualizar.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.00040 | $0.00457 |
| Opus 5 | $0.00020 | $0.00229 |
| Sonnet 5 | $0.00008 | $0.00091 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
git-actualizar 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 12d 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.
What it actually says
git-actualizar
Dos fases independientes. No crea, no resetea ni modifica vitals/ops/session.yaml.
Instrucciones upstream (Markdown): references/upstream-check.md · spec vitals/specs/dt-upstream-config.md.
Fase A — Proyecto (siempre)
-
Resolver
git_root(si existevitals/workspace.yaml, respetar multi-proyecto). -
Ejecutar:
git fetch origin git pull --rebase -
Reportar breve: commits traídos o "al día", rama actual, conflictos si los hay.
Fase B — Framework DT (consulta only)
Seguir todo references/upstream-check.md.
Resumen: leer vitals/config/dt-upstream.md, comparar semver con tags de dt-upstream, avisar si hay release nueva → ofrecer /actualizar-dt. No checkout. No scripts Ruby.
Post-Fase A (opcional)
Tras pull grande en rules/commands/skills del proyecto, sugerir /setup o post-sync-pipeline.md.
Sesión
Si no existe vitals/ops/session.yaml or operator.id vacío → una línea: "Para trabajar con identidad en este repo, usá /yo."
Conflictos (Fase A)
- Listar archivos en conflicto; no
push --forceen main/master. - Tras resolver:
/guardarsi va a commitear.
No hacer
- No tocar
vitals/ops/session.yaml. - No ejecutar apply de sync desde
/actualizar. - No invocar scripts Ruby para Fase B.
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.
- 12d ago First seen · 48 lines · 40 tokens per session scan A c03a9f0bc648
git-actualizar is a skill published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 457 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
dale-loop-pr
Monitor or repair one existing pull request using current review and CI evidence. Use for PR babysitting, scoped fixes, or carrying a PR to merge-ready state.
dale-loop-repo
Maintain a repository on a requested recurring cadence using bounded priorities and live evidence. Use for recurring engineering triage or repository maintenance.
new-gh-issue-orchestration
Orchestrates a GitHub-issue-driven delivery workflow from issue intake to PR creation using reviewer-first then worker execution. Invoked when the user provides a GitHub issue link/number and asks to start end-to-end delivery.
github-release-management
GitHub release orchestration — automated versioning, testing, deployment, and rollback. Use when cutting a release, tagging a version, drafting release notes, or coordinating a deploy/rollback workflow.
agentic-jujutsu
Use when multiple agents need to write to the same repo concurrently without file-lock stalls — applies claim-before-write, parallel branch fan-out, and semantic 3-way merge to achieve 87% auto-conflict resolution.
session-checkpoint
Use when you want to save a timestamped snapshot of current session state (tasks, evidence, purpose) to docs/session-logs/ for crash recovery or handoff.