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.00043 | $0.03250 |
| Opus 5.5 | $0.00017 | $0.01300 |
| Sonnet 5.5 | $0.00009 | $0.00650 |
| Haiku 4.5 | $0.00004 | $0.00325 |
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 2d 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 — 203 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.
Invariante — dos semver distintos
VERSION (raíz) es solo la versión del producto de este repo. framework_version en vitals/config/dt-upstream.md es solo la del DT.
- Nunca copies, sugieras ni escribas el semver del DT en
VERSION,package.jsonni el badge del producto. - Nunca uses
framework_versioncomo si fuera la app. - Si el producto ya tiene semver (
package.jsonen raíz/frontend/backend/apps/*, oVERSIONdistinta del DT) → conservala y hacé bump con los criterios de abajo. - Si el proyecto es nuevo (no hay semver de producto) → partí de
initial_semver(0.1.0). No heredes el número del DT.
El script lo garantiza. Antes de bumpear:
./scripts/project-resolve-version.sh
Leé DT_PRODUCT_VERSION, DT_FRAMEWORK_VERSION y DT_VERSION_ACTION. Si bump/sync fallan porque VERSION coincide con el DT, resolvé; no pises el package.json a mano.
Invocaciones
| Comando | Bump | Cuándo |
|---|---|---|
/guardar |
lo elige la IA | Hay cambios a commitear |
/guardar release patch|minor|major |
el dígito nombrado | El mensaje ya lo especifica; no reclasificar |
| Sin cambios en el repo | — | No bump; informar "sin cambios" |
/guardar release a secas = patch. También vale nombrarlo en prosa (“bumpeá major”, “esto es un patch”).
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.yamlvitals/ops/canonical-checkout.yamlvitals/ops/collaboration.local.yamlvitals/ops/context-profile.yaml.cursor/rules/99-perfil-local.mdc.claude/rules/99-perfil-local.md.agents/rules/99-perfil-local.md.env,.env.local,*.credentialsvitals/workspace.yamlvitals/config/drive-context.yamlvitals/config/gmail-context.yamlvitals/config/calendar-context.yamlvitals/config/google-apps.yamlvitals/work/inbox/**/draft-*
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.
- 2d ago Changed · +1 lines a52e3975a91e
- 3d ago Changed · +4 lines 92a1751e2332
- 25d ago Changed 0a8e5f767306
- 29d ago Changed · +42 lines 8d77f58fa693
- 1mo ago Changed · +59 lines · +7 tokens per session da779aaf4a45
- 1mo 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 yesterday), licensed MIT. It adds 43 tokens to every session and 3,250 once invoked, about $0.0002 per session on Opus 5.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 an OMH deploy-and-monitor workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
release-notes-check
Check a supplied release note for its owner and rollback note.
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…