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/dt-configWrote 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-config)<a href="https://agentmods.dev/skills/mazalucas/el-dt-lightweight-army/dt-config"><img src="https://agentmods.dev/badge/skills/mazalucas/el-dt-lightweight-army/dt-config/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-config"><img src="https://agentmods.dev/badge/skills/mazalucas/el-dt-lightweight-army/dt-config.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.00046 | $0.00631 |
| Opus 5.5 | $0.00018 | $0.00252 |
| Sonnet 5.5 | $0.00009 | $0.00126 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
dt-config 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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dt-config
El usuario elige cuánto contexto de reglas queda activo en esta máquina. El perfil no lleva nombre y no va a Git.
No exige /yo. No leas ni escribas session.yaml, roster.yaml ni collaboration.yaml.
Archivos
| Archivo | Git | Rol |
|---|---|---|
vitals/ops/context-profile.yaml |
No | Elección (preset + reglas en siempre) |
.cursor/rules/99-perfil-local.mdc |
No | Cuerpos que Cursor carga en cada mensaje |
.claude/rules/99-perfil-local.md |
No | El mismo perfil en Claude |
.agents/rules/99-perfil-local.md |
No | El mismo perfil en Antigravity |
Las cuatro fijas (personalidad, protocolos, especialistas, equipo) no se apagan. El perfil solo suma reglas.
Si todavía no eligió
- No preguntes nada fuera del panel.
- En Cursor, corré
ruby scripts/dt-context-profile.rb panely publicá esa stdout como visualización inline (fragmento HTML, sin envolverlo en<html>). El usuario toca los botones y los interruptores. La frase en negrita es la respuesta. - Si no hay visualización, corré
ruby scripts/dt-context-profile.rb texty mostrá esa salida. - Parar. La configuración ocurre cuando responde.
Cuando responde
Pasá su frase tal cual:
ruby scripts/dt-context-profile.rb apply --phrase "LA FRASE"
Frases válidas: Recomendado, Docs, Código, Web, Números, o Recomendado, y Documentación en siempre (varias unidas con coma y una «y» antes de la última). También valen los rótulos de los botones (Trabajar en docs, etc.).
- Exit 0: mostrale el resumen del script, en criollo. El perfil ya quedó escrito.
- Exit 2: decile la frase que no entró y volvé a mostrar el panel.
No edites el YAML ni los .mdc a mano. No los commitees.
Qué ve el usuario
- No se apaga — personalidad, protocolos, especialistas, equipo.
- Usar recomendado — el resto entra solo cuando el tema aparece.
- Trabajar en docs / código / web / números — esas reglas pasan a cada mensaje.
- Un interruptor arma la frase
Recomendado, y … en siempre.
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 First seen · 53 lines · 46 tokens per session scan A 29bc84412be5
dt-config is a skill published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 631 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-09-24.
Other skills, from other repositories
github-release-management
GitHub release orchestration — automated versioning, testing, deployment, and rollback. Use when cutting a release, tagging a version, drafting release notes, or coordinating a deploy/rollback workflow.
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) development methodology with multi-agent orchestration. Use when running a structured spec-to-code workflow or decomposing a feature through the SPARC phases.
dale-loop-watch
Monitor a changing source or condition on a cadence, persist the last meaningful observation, and notify or act only when a user-defined change occurs. Use for watching pull requests, issues, releases, prices, availability, feeds, pages, dashboards, or other external state.
swarm-advanced
Advanced swarm-orchestration patterns for research, development, testing, and complex distributed workflows. Use when scaling beyond a few agents, designing dynamic swarm topologies, or coordinating large parallel agent workloads.
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.
session-checkpoint
Use when you want to save a timestamped snapshot of current session state (tasks, evidence, purpose) to docs/session-logs/ for crash recovery or handoff.