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/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/commands/mazalucas/el-dt-lightweight-army/guardar)<a href="https://agentmods.dev/commands/mazalucas/el-dt-lightweight-army/guardar"><img src="https://agentmods.dev/badge/commands/mazalucas/el-dt-lightweight-army/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/commands/mazalucas/el-dt-lightweight-army/guardar"><img src="https://agentmods.dev/badge/commands/mazalucas/el-dt-lightweight-army/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.00000 | $0.00200 |
| Opus 5.5 | $0.00000 | $0.00080 |
| Sonnet 5.5 | $0.00000 | $0.00040 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
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 1mo 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
/guardar
Grupo: Rutina del día a día En una frase: Guardar cambios — bump, commit y push al remoto de este repo. El DT oficial solo con /oficial activo. Cuándo: Al cerrar bloque con cambios. El dígito lo elige la IA; si nombrás patch, minor o major, usa ese. Quién: Cualquier operador del repo.
Ejecutá el skill git-guardar — .cursor/skills/git-guardar/ y .agents/skills/git-guardar/.
Generado desde vitals/config/commands-meta.yaml — corré scripts/sync-commands-from-meta.sh.
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.
- 1mo ago Changed 92608ac4c2cc
- 1mo ago First seen · 19 lines · 0 tokens per session scan A 0d30f1e01177
guardar is a command published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 200 tokens. 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
ia-changelog
Create engaging changelogs for recent merges to main branch.
release
Bump version, commit, push, mirror to ai-skills, and update local plugin.
repo-sprint
Collection health triage and work-session kickoff (dirty, unpushed, active, release candidates, audit gaps, stale, unpublished).
close-track
Close a completed track — run quality gate, update conductor state, commit, and optionally handle the git branch.
finishing-a-development-branch
Complete development work — verify tests, push branch, create PR.
run-release
Orchestrate a tagged release using the release workflow.