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 dt-sessiongit 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/dt-session)<a href="https://agentmods.dev/skills/mazalucas/el-dt-lightweight-army/dt-session"><img src="https://agentmods.dev/badge/skills/mazalucas/el-dt-lightweight-army/dt-session/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/dt-session"><img src="https://agentmods.dev/badge/skills/mazalucas/el-dt-lightweight-army/dt-session.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.00039 | $0.00585 |
| Opus 5 | $0.00019 | $0.00293 |
| Sonnet 5 | $0.00008 | $0.00117 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
dt-session 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.
What it actually says
dt-session
La sesión solo existe tras /yo. No uses plantillas con placeholders ni participantes de ejemplo del repo.
Archivos
| Archivo | Git | Acción |
|---|---|---|
vitals/ops/session.yaml |
No | Crear/actualizar al validar identidad |
vitals/config/roster.yaml |
Sí | Append solo si operador nuevo (datos reales del usuario) |
vitals/config/roles.yaml |
Sí | Opcional: si roles[] tiene entradas, validar o sugerir; si está vacío, rol = texto libre |
vitals/work/inbox/{id}/ |
Sí | mkdir -p |
Pasos
- Si no existe
vitals/ops/session.yaml→ se crea al confirmar identidad. - Si hay
operator.id+operator.name→ "¿Seguís como {name}?"- Sí → actualizar
identified_at. - No → identificación nueva (paso 3).
- Sí → actualizar
- Preguntar quién trabaja hoy: nombre (y rol si el usuario no lo dijo).
id= slug minúsculas sin espacios (derivado del nombre si hace falta, confirmar con el usuario).- Rol: leer
vitals/config/roles.yaml. Sirolestiene ítems → ofrecer lista o aceptar si el usuario ya nombró uno válido. Siroles: []o no existe → guardar el rol tal como lo diga el usuario (sin imponercontributor/maintainer/etc.). - Buscar
idenroster.yaml→team[]. Si nuevo: append conname,role,emailopcional,registered_at(ISO 8601) y actualizarupdateden el archivo. Si ya está: no duplicar ni reescribir con datos de ejemplo. - Escribir
session.yamlconoperator(id, name, role, email, inbox_path),identified_at,session_started. mkdir -p vitals/work/inbox/{id}/- Confirmar id, nombre, rol, inbox. Si hubo alta en roster: recordar
/guardarpara subirroster.yaml.
No hacer
- No commitear
session.yaml. - No escribir en
roster.yamlnombres/roles de ejemplo del template ni placeholders. - No inventar participantes ni roles por defecto.
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 · 38 lines · 39 tokens per session scan A e27aea4cffac
dt-session is a skill published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 585 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-project
Carry an engineering project through independently reviewable changes and PRs. Use when a requested project needs multiple PRs or explicit end-to-end delivery through merge.
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.
codex-symphony
Install and operate a portable OpenAI Symphony + Linear orchestration setup in any Git repository. Use when the user wants a one-command local Symphony runner, a reusable WORKFLOW template, background launch scripts, or a Codex wrapper that restarts Symphony automatically when reopening the CLI.
sparc-pipeline
Use when you need to run the full 5-phase SPARC methodology (Specification→Pseudocode→Architecture→Refinement→Completion) for a complex feature. Each phase has explicit done-criteria gates.
scope-lock
Use when you want to lock the session to a specific scope description, injecting it into purpose-gate context and optionally blocking out-of-scope tool calls.
workflow-run
Use when you need to execute a DAG-structured workflow template from SKILLS/ORCHESTRATION FRAMEWORK/workflow-templates/.