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 lubluniky/dale --skill dale-lensesgit clone --depth 1 https://github.com/lubluniky/daleWrote 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/lubluniky/dale/dale-lenses)<a href="https://agentmods.dev/skills/lubluniky/dale/dale-lenses"><img src="https://agentmods.dev/badge/skills/lubluniky/dale/dale-lenses/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/lubluniky/dale/dale-lenses"><img src="https://agentmods.dev/badge/skills/lubluniky/dale/dale-lenses.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00135 | $0.01265 |
| Opus 5.5 | $0.00054 | $0.00506 |
| Sonnet 5.5 | $0.00027 | $0.00253 |
| Haiku 4.5 | $0.00014 | $0.00127 |
Grade A, and why
dale-lenses 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dale Lenses
Change the representation of a hard problem before changing the answer. Apply a specific epistemic method with an observable artifact and a stop rule; never simulate rigor by naming several frameworks and repeating the same opinion.
Keep the method bounded
- Preserve the user's current phase. Analyze, decide, plan, or implement only to the extent requested; invoking a lens does not authorize execution.
- Require a bounded question. When the user is still discovering the goal, options, taste, or priorities, keep or move the conversation to ordinary brainstorming instead of imposing a lens prematurely.
- Stay in the current task. Do not create Codex tasks or subagents merely to manufacture perspectives. Use tools only when actual evidence is needed and already authorized.
- Separate observations, inferences, assumptions, preferences, and unknowns.
- Redact secrets, credentials, raw environment values, personal data, private transaction identifiers, and other sensitive operational evidence before it enters a tool call, artifact, or response.
- Select one primary lens. Add one challenging lens only when it makes a materially different prediction, exposes a different failure mode, or could reverse the decision.
- Honor a lens named by the user. If it does not fit the problem, explain the mismatch briefly and offer the closest fitting lens instead of silently substituting it.
- Decline the method when ordinary reasoning is sufficient. “No useful reframe” is better than framework theatre.
Select by problem signature
Read references/lens-contracts.md completely before applying a lens.
| Lens | Use when the core uncertainty concerns | Required artifact |
|---|---|---|
causal |
competing explanations or interventions | rival causal models and a discriminating observation |
systems |
feedback, delays, recurrence, or second-order effects | bounded feedback model with testable predictions |
temporal |
retries, ordering, concurrency, TTL, or version skew | state transitions and a concrete interleaving trace |
conservation |
missing or duplicated money, events, jobs, inventory, or authority | scoped balance equation and residual |
invert |
consequential failure paths or ineffective safeguards | minimal failure recipe, controls, and tripwires |
constraint |
throughput stays flat despite local optimization | evidenced system constraint and migration signal |
contradiction |
two necessary requirements appear mutually exclusive | exact coupling and a separation that tests both sides |
decide |
costly choice under uncertainty or irreversibility | options, states, regret, reversibility, and value of information |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 117 lines · 135 tokens per session scan A 69d9e310416f
dale-lenses is a skill published in the GitHub repository lubluniky/dale (54 stars, last pushed 1mo ago), licensed MPL-2.0. It adds 135 tokens to every session and 1,265 once invoked, about $0.0005 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-30.
Other skills, from other repositories
loop-graph
Use only when the user explicitly invokes /loop-graph or names this skill. Compiles a custom loop-graph run. Do not use unless named. Existing runtime nodes are self-contained.
loop-research
Use only when the user explicitly invokes /loop-research or names this skill. Authors a loop-research run. Do not use unless named. Do not execute or resume generated runtime node files.
longgraph
Use only when the user explicitly invokes /longgraph or names this skill. Routes and authors a durable longgraph run. Do not use unless named. Do not execute or resume generated runtime node files.
loop-converge
Use only when the user explicitly invokes /loop-converge or names this skill. Authors a loop-converge run. Do not use unless named. Do not execute or resume generated runtime node files.
loop-deliver
Use only when the user explicitly invokes /loop-deliver or names this skill. Authors a loop-deliver run. Do not use unless named. Do not execute or resume generated runtime node files.
atelier
Atelier design intelligence (El DT + Impeccable). Use for UI/UX design, craft, critique, audit, polish, anti-slop, tokens, decks, and frontend iteration. Invoke /atelier [target]. Covers landing, dashboard, product UI, components, motion, a11y, and design system alignment.