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-bootstrapgit 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-bootstrap)<a href="https://agentmods.dev/skills/mazalucas/el-dt-lightweight-army/dt-bootstrap"><img src="https://agentmods.dev/badge/skills/mazalucas/el-dt-lightweight-army/dt-bootstrap/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-bootstrap"><img src="https://agentmods.dev/badge/skills/mazalucas/el-dt-lightweight-army/dt-bootstrap.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.00059 | $0.00984 |
| Opus 5 | $0.00030 | $0.00492 |
| Sonnet 5 | $0.00012 | $0.00197 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade A, and why
dt-bootstrap 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dt-bootstrap
Convierte el template El DT en la base de tu propio proyecto: lo promueve a la raíz, suelta el remoto del template y deja el repo listo para tu trabajo. Es una operación irreversible → cae bajo el gate duro (vitals/specs/precedence.md): siempre dry-run + confirmación explícita + working tree limpio.
Pre-requisitos
- Sesión válida (
/yo). - Working tree limpio (
git status). Si hay cambios sin commitear → detener y pedir/guardaro stash. - Confirmar destino: ¿el DT está en una subcarpeta del proyecto o ya es la raíz?
Pasos (con dry-run primero)
-
Dry-run: listar exactamente qué se va a mover, qué remoto se va a soltar, registro de
dt-upstream, y qué se va a resetear. Mostrarlo y pedir confirmación. No ejecutar nada hasta el OK. -
Promover al raíz (si está en subcarpeta): mover el contenido del DT a la raíz del proyecto destino sin pisar archivos existentes; ante colisión, preguntar.
-
Registrar upstream del template (antes de soltar
origin):TEMPLATE_URL="$(git remote get-url origin)" git remote add dt-upstream "$TEMPLATE_URL" # idempotente si ya existeCapturar
FRAMEWORK_VERSION="$(cat VERSION)"(semver DT actual).Crear o actualizar
vitals/config/dt-upstream.md(desdevitals/config/dt-upstream.example.md):--- version: 1 mode: consumer framework_version: "<FRAMEWORK_VERSION>" source: remote: dt-upstream ref: main --- -
Soltar el remoto del template (irreversible):
git remote remove originOfrecer:
git remote add origin <tu-repo>y/ogit initfresco si el usuario quiere historial limpio (sin el del template). -
Resetear estado del template:
VERSION→ reiniciar a0.1.0del nuevo proyecto (preguntar). La versión del framework queda enframework_versiondevitals/config/dt-upstream.md, no enVERSIONraíz.vitals/config/project-version.yaml— crear desdeproject-version.yaml.example:initialized: false,auto_bump: none,initial_semver: "0.1.0"- Discover
package.jsonen raíz,frontend/,backend/,apps/*/package.json→sync_paths ./scripts/project-sync-version.sh— unificar semver en front/back/monorepo- Spec:
vitals/specs/project-version.md
vitals/config/roster.yaml→team: [].vitals/pulse/→ limpiar entries de ejemplo (conservarcurrent.mdcomo puntero vacío).- Banner/README → placeholder del nuevo proyecto (preguntar antes de reescribir).
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 · 72 lines · 59 tokens per session scan A 6f76a7a07e61
dt-bootstrap is a skill published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 984 once invoked, about $0.0003 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-pr
Monitor or repair one existing pull request using current review and CI evidence. Use for PR babysitting, scoped fixes, or carrying a PR to merge-ready state.
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.
new-gh-issue-orchestration
Orchestrates a GitHub-issue-driven delivery workflow from issue intake to PR creation using reviewer-first then worker execution. Invoked when the user provides a GitHub issue link/number and asks to start end-to-end delivery.
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.
agentic-jujutsu
Use when multiple agents need to write to the same repo concurrently without file-lock stalls — applies claim-before-write, parallel branch fan-out, and semantic 3-way merge to achieve 87% auto-conflict resolution.
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.