Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Mazalucas/El-DT-Lightweight-Armynpx agentmods add skills/mazalucas/el-dt-lightweight-army/git-guardarWrote 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-guardar)<a href="https://agentmods.dev/skills/mazalucas/el-dt-lightweight-army/git-guardar"><img src="https://agentmods.dev/badge/skills/mazalucas/el-dt-lightweight-army/git-guardar/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-guardar"><img src="https://agentmods.dev/badge/skills/mazalucas/el-dt-lightweight-army/git-guardar.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.00036 | $0.00853 |
| Opus 5 | $0.00018 | $0.00426 |
| Sonnet 5 | $0.00007 | $0.00171 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
git-guardar 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 11d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
git-guardar
Spec versión: vitals/specs/project-version.md.
Invocaciones
| Comando | Bump | Cuándo |
|---|---|---|
/guardar |
patch | Hay cambios a commitear (guardar = entrega con nueva versión) |
/guardar release minor |
minor | Mismo, bump minor explícito |
| Sin cambios en el repo | — | No bump; informar "sin cambios" |
/guardar release = alias de patch (opcional).
Pre-requisitos
vitals/ops/session.yamlconoperator.id— pedir/yosalvo pedido explícito de avanzar sin sesión.vitals/config/dt-upstream.md→mode:canonical|consumer.- Opcional:
git fetch; si behind →/actualizar.
Exclusiones (nunca stage)
vitals/ops/session.yaml.env,.env.local,*.credentialsvitals/workspace.yamlvitals/work/inbox/**/draft-*
Flujo (ambos modos)
-
git status— si no hay cambios (salvo archivos excluidos) → detener sin bump. -
git reset HEAD vitals/ops/session.yamlsi quedó staged. -
Bump (ver excepciones abajo):
./scripts/project-bump-version.sh patch # o minor si pidió release minor -
./scripts/project-sync-version.sh— README,framework_version, front/back/tools. -
Stage selectivo + archivos tocados por bump/sync (
VERSION, README, etc.). -
./scripts/dt-doctor.sh— corregir ERRORES. -
Commit — primera línea siempre con la versión nueva:
v{X.Y.Z} ({operator_id}): {resumen corto} -
git push origin HEAD— sin--forceen main/master. -
Tag tras push OK:
./scripts/dt-tag-version.sh --push --message "Release v$(cat VERSION)"Tras bump, el tag debe ser nuevo. Si falla (tag en otro commit sin bump previo) → reportar error.
Excepciones de bump
| Caso | Bump |
|---|---|
Consumer primer /guardar (initialized: false) |
No — reset VERSION → initial_semver (0.1.0), luego sync |
/guardar con cambios |
patch (default) |
/guardar release minor |
minor |
| Sin cambios | No ejecutar guardar |
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.
- 11d ago First seen · 97 lines · 36 tokens per session scan A 0147f66d9028
git-guardar is a skill published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 853 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
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
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…
omh-deploy-and-monitor
This is a Hermes-native deploy-and-monitor workflow skill.
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
finalize
Finalize orphaned recordings - stop processes, compress, push to orphan branch. TRIGGERS - finalize recording, stop asciinema, orphaned recording.