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-gmailgit 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-gmail)<a href="https://agentmods.dev/skills/mazalucas/el-dt-lightweight-army/dt-gmail"><img src="https://agentmods.dev/badge/skills/mazalucas/el-dt-lightweight-army/dt-gmail/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-gmail"><img src="https://agentmods.dev/badge/skills/mazalucas/el-dt-lightweight-army/dt-gmail.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.00971 |
| Opus 5.5 | $0.00018 | $0.00388 |
| Sonnet 5.5 | $0.00009 | $0.00194 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
dt-gmail 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 21d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dt-gmail
Integración opcional de Gmail vía el MCP oficial del IDE. google-drive-dt está descontinuado.
Spec: vitals/specs/google-apps-mcp.md. Guía usuario: docs/02_guides/drive-cerebro-setup.md (DOC-GUIDE-009). ADR: DOC-DEC-006.
No abras el runbook de IT ni fichas de Google Cloud en este chat.
Prerequisitos
Sesión (/yo). Plugin, MCP Store o conector oficial de Gmail. Sin JSON Desktop ni Node.
Archivos
| Archivo | Git | Rol |
|---|---|---|
vitals/config/google-apps.yaml |
No | Apps habilitadas |
vitals/config/gmail-context.yaml |
No | Etiquetas / queries |
vitals/config/gmail-context.yaml.example |
Sí | Plantilla |
Flujo /gmail
- Confirmar
/yo. - Embudo: ¿solo Gmail o también Drive y Calendar?
- Instalar el oficial con el procedimiento único de
vitals/specs/google-apps-mcp.md§ Instalar. Slug en Cursor:gmail. Marketplace / Store primero. No recorras Google Cloud Console. - Esperar tools de búsqueda/lectura/draft. Si no hay, Freno — no inventar el inbox.
- Selector de contexto. Actualizar
google-apps.yaml(gmail: true) ygmail-context.yaml. - Legado
google-drive-dt→ ofrecer--remove-legacycuando el oficial ya lea mail.
Si solo quieren cambiar etiquetas y Gmail ya está → selector.
Freno
Si no hay tools o no aparece Authenticate:
- Parar. No seguir al selector. No inventar el inbox.
- No recorras Google Cloud Console.
- No abras el runbook de IT. No armes un JSON con
clientId. - Decí solo: Falta el client OAuth de la organización. Pedíselo a IT. Si no hay IT, usá la documentación oficial de Google Workspace MCP en tu navegador. El DT no recorre Google Cloud Console ni pega secrets.
Selector de contexto
No leer “todo el correo” salvo sync_mode: full_mailbox pedido explícito.
- Mostrar
gmail-context.yamlsi existe. - Pedir etiquetas y/o queries (
from:,newer_than:,label:) con propósito. - Si hay
list_labels/list_email_labels, ayudar a elegir. - Escribir el YAML (schema del
.example). No va a Git.
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.
- 21d ago Changed · +18 lines e6760f865db5
- 22d ago Changed · -5 lines · -3 tokens per session 6d48fb563590
- 29d ago First seen · 70 lines · 49 tokens per session scan A d395c361bb03
dt-gmail 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 971 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-29.
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.