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/gonzalezpazmonica/saviaWrote 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/gonzalezpazmonica/savia/backlog-git)<a href="https://agentmods.dev/commands/gonzalezpazmonica/savia/backlog-git"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/savia/backlog-git/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/gonzalezpazmonica/savia/backlog-git"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/savia/backlog-git.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.00013 | $0.01026 |
| Opus 5.5 | $0.00005 | $0.00410 |
| Sonnet 5.5 | $0.00003 | $0.00205 |
| Haiku 4.5 | $0.00001 | $0.00103 |
Grade A, and why
backlog-git 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 28d 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.
This is a copy
100% identical to backlog-git — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/backlog-git — Versionado de backlogs
Reglas: @docs/rules/domain/backlog-git-config.md Dependencia: @docs/rules/domain/savia-hub-config.md · @docs/rules/domain/client-profile-config.md
Subcomandos
/backlog-git snapshot {client} {project}
Captura una foto del estado actual del backlog.
Flujo:
- Verificar SaviaHub + cliente + proyecto existen
- Detectar fuente del backlog (Azure DevOps, Jira, GitLab, Savia Flow, manual)
- Extraer PBIs/items con: ID, título, estado, asignado, estimación, prioridad
- Generar fichero markdown:
backlog-snapshots/YYYYMMDD-HHMMSS.md - Incluir frontmatter con metadatos (fuente, total items, fecha, versión)
- Commit en SaviaHub:
[backlog-git] snapshot: {client}/{project} ({N} items) - Si remote + no flight-mode → push
Output:
📸 Snapshot del backlog capturado
Cliente: {client} · Proyecto: {project}
Fuente: {source}
Items: {N} total ({done} done, {in-progress} in-progress, {new} new)
Fichero: backlog-snapshots/YYYYMMDD-HHMMSS.md
/backlog-git diff {client} {project} [--from REF] [--to REF]
Compara dos snapshots del backlog.
Flujo:
- Sin flags → comparar último snapshot con el anterior
- Con
--from/--to→ comparar snapshots específicos (fecha o índice) - Calcular deltas: items añadidos, eliminados, modificados (estado/estimación/asignado)
- Detectar re-estimaciones (estimación original vs actual)
- Mostrar resumen formateado
Output:
📊 Diff del backlog: {from} → {to}
Añadidos: {N} items | Eliminados: {N} | Modificados: {N}
Re-estimados: {N} items (Δ total: +{H}h)
Estado: {N} cambiaron de estado
/backlog-git rollback {client} {project} {snapshot-ref}
Genera un informe de restauración (NO modifica el backlog original).
Flujo:
- Cargar snapshot referenciado
- Comparar con estado actual → generar diff inverso
- Listar acciones necesarias para restaurar al estado del snapshot
- NUNCA ejecutar automáticamente — solo informar al PM
- El PM decide si aplica manualmente en el PM tool
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.
- 28d ago Changed a9c7aee7d513
- 1mo ago First seen · 120 lines · 13 tokens per session scan A b432feafbe34
backlog-git is a command published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 1,026 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to backlog-git, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
wtfp:contribute
Guide a bounded WTF-P contribution from branch creation through a reviewable change request.
contribute
Guide a bounded WTF-P contribution from branch creation through a reviewable change request.
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits.
gsd:quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
standup
Review my git commits from the past workday and generate a standup summary.
company-repo
Gestionar el repositorio Company Savia: crear, conectar, estado, sincronizar. El repositorio compartido de la empresa para conocimiento, mensajería y estado.