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/rules/mazalucas/el-dt-lightweight-army/18-drive-contexto)<a href="https://agentmods.dev/rules/mazalucas/el-dt-lightweight-army/18-drive-contexto"><img src="https://agentmods.dev/badge/rules/mazalucas/el-dt-lightweight-army/18-drive-contexto/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/rules/mazalucas/el-dt-lightweight-army/18-drive-contexto"><img src="https://agentmods.dev/badge/rules/mazalucas/el-dt-lightweight-army/18-drive-contexto.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.00505 |
| Opus 5 | $0.00000 | $0.00253 |
| Sonnet 5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
18-drive-contexto 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 7d 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
Google Drive como contexto del cerebro
Integración opcional vía MCP. Aplica cuando existe vitals/config/drive-context.yaml o el usuario invocó /drive.
Cuándo consultar Drive
- El usuario pide contexto que probablemente vive en Drive ("buscá en mis briefs", "qué dice el doc de X").
- Necesitás información de carpetas registradas en
drive-context.yaml. - Generar entregables a partir de documentos en Drive sin copiarlos al repo (solo lectura).
Límites obligatorios
- Solo carpetas registradas — con
sync_mode: selective, consultar únicamente dentro de losfolders[].iddel registro (queries'<folderId>' in parentso búsqueda acotada). Confull_drive, advertir al usuario que la búsqueda es amplia. - Solo lectura — scope
drive.readonly; no crear, editar, mover ni borrar archivos en Drive. - Consulta dirigida — listar/buscar primero; leer solo archivos relevantes. No volcar carpetas enteras al contexto.
- Charter no-secrets — no persistir en Git tokens, credenciales ni contenido sensible de Drive sin confirmación (
vitals/charter/no-secrets.md). - Drive ≠ memoria del repo — Drive es biblioteca consultable; destilar a
vitals/odocs/solo si el usuario pide guardar algo en el cerebro compartido.
Resolución de carpeta
Antes de buscar, leer vitals/config/drive-context.yaml:
- Matchear la intención del usuario con
purposeykeywordsde cada carpeta. - Si hay ambigüedad, preguntar qué carpeta usar.
- Citar siempre nombre de carpeta + archivo consultado en la respuesta.
Referencias
- Skill:
.cursor/skills/dt-drive/· command/drive - Guía usuario:
docs/02_guides/drive-cerebro-setup.md(DOC-GUIDE-009) - Admin OAuth:
docs/06_operations/drive-google-cloud-admin.md(DOC-OPS-002)
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.
- 7d ago First seen · 38 lines · 0 tokens per session scan A 93148bc0e51a
18-drive-contexto is a cursor rule published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 505 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 cursor rules, from other repositories
aictx
Cursor rule "aictx" from oldskultxo/aictx, covering aictx, priority model, default loop, inspection and advanced tools and what to record.
session-distill
How to distill a long work session into ContextForge so a fresh session can resume cleanly. Invoke when the user asks to distill/hand off/checkpoint the session, when context is getting bloated and work is unfinished, or before deliberately starting a new session on the same task.
vectr
Vectr tool usage rules for AI-assisted development.
801-bedtime-protocol
description: WHEN user mentions "Bedtime Protocol" THEN immediately follow the step-by-step process in the README.md file globs: /.
archive
Cursor rule "archive" from savagelysubtle/BIG-BRAIN-Memory-Bank, covering task archiving protocol, 📁 archive setup, 📋 archive format, task: [task name] (v1.0) and implementation results.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.