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/atelierWrote 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/atelier)<a href="https://agentmods.dev/skills/mazalucas/el-dt-lightweight-army/atelier"><img src="https://agentmods.dev/badge/skills/mazalucas/el-dt-lightweight-army/atelier/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/atelier"><img src="https://agentmods.dev/badge/skills/mazalucas/el-dt-lightweight-army/atelier.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.00072 | $0.03711 |
| Opus 5.5 | $0.00029 | $0.01484 |
| Sonnet 5.5 | $0.00014 | $0.00742 |
| Haiku 4.5 | $0.00007 | $0.00371 |
Grade A, and why
atelier 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atelier — design intelligence (El DT)
Router unificado. Upstream: Impeccable vendoreado vía tools/atelier/.
DT session gate (El DT)
Before writing files in the repo:
- Read
vitals/ops/session.yaml. If missing oroperator.idempty → stop and ask the user to run/yo. - Design context canonical path:
.agents/design-context.md(not separate PRODUCT.md/DESIGN.md unless exporting).
DT context loader
Run once per session (not per sub-command):
node tools/atelier/generated/scripts/context.adapter.mjs
Optional target for monorepos:
node tools/atelier/generated/scripts/context.adapter.mjs --target <path>
- If output reports
NO_DESIGN_CONTEXT, stop and followtools/atelier/generated/references/init.md. - Imports
.agents/product-marketing.mdwhen present (see design-context skill). UPDATE_AVAILABLE: offer/atelier actualizar(DT maintainer sync), then continue.
Register references (DT paths)
Impeccable 4 names visitor modes. Map register from design-context:
design-context register |
Mode | File |
|---|---|---|
| brand (marketing, landing, portfolio) | Persuade | Modes in this skill + tools/atelier/generated/references/new-work.md |
| product (app, dashboard, tool) | Operate | tools/atelier/generated/references/operate.md |
Do not create duplicate PRODUCT.md/DESIGN.md.
DT-native subcommands
| Command | Action |
|---|---|
/atelier select [brief] |
ruby scripts/dt-design-select.rb "brief" + skill design-selector |
/atelier read |
skill design-read — V/M/D dials |
/atelier tokens |
skill design-tokens |
/atelier template [name] |
skill ui-templates or --scaffold → tools/atelier/starters/ |
/atelier deck [brief] |
references/deck.md — brand manual gate + slide-deck-html |
/atelier actualizar |
skill atelier-actualizar — sync Impeccable upstream |
DT extensions (after Impeccable setup)
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 Changed · -97 lines bb4e72d87a7b
- 1mo ago First seen · 269 lines · 72 tokens per session scan A e25632b11299
atelier is a skill published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed yesterday), licensed MIT. It adds 72 tokens to every session and 3,711 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
omh-apple-design
This is an OMH apple-design workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
design-craft
Design or substantially improve user-facing interfaces with a product-specific visual direction, content hierarchy, and rendered critique. Use for new screens, landing pages, redesigns, typography/layout work, or UI that feels generic or AI-generated. For small fixes, preserve the existing design without starting a…
product-research
Find and compare current FF&E candidates from a design brief, with sourced purchasing facts and optional CSV-library save. Use to research or source products; not to match from an image or pair coordinating items.
frontend-composition
Implement polished self-contained HTML interfaces with semantic structure, maintainable CSS, realistic content, and purposeful visual hierarchy.
law-of-similarity
Apply the Law of Similarity — shared colour, shape, or size signals that elements belong to one category. Use when signalling relationships across distance. For grouping by position, use law-of-proximity.
form-design
Design a form end to end — field order, grouping, validation, and completion. Use when the artifact is a form. For product-wide error strategy use error-handling-ux; for first-run signup use onboarding-design.