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 dasTholo/lean-md --skill lmd-rendering-skillsgit clone --depth 1 https://github.com/dasTholo/lean-mdWrote 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/dastholo/lean-md/lmd-rendering-skills)<a href="https://agentmods.dev/skills/dastholo/lean-md/lmd-rendering-skills"><img src="https://agentmods.dev/badge/skills/dastholo/lean-md/lmd-rendering-skills.svg" alt="Measured on agentmods" 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.00045 | $0.00558 |
| Opus 5 | $0.00023 | $0.00279 |
| Sonnet 5 | $0.00009 | $0.00112 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
lmd-rendering-skills 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 8d 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
lmd-rendering-skills
Every lmd-* skill is a delegation stub. Its body lives in the version-pinned pack
@dastholo/lean-md-skills and renders on demand, one phase at a time. Never read a
body or companion file from disk.
The call
In the lean-ctx addon topology — lean-md aggregated behind the lean-ctx gateway,
the common case and the one this skill exists for — ctx_md_render is NOT a direct
tool. lean-md is a separate stdio MCP server, reachable only through the gateway:
ctx_tools(action="call", tool="lean-md::ctx_md_render",
arguments={"skill": "<skill>", "phase": "<phase>"})
Pass exactly one of phase or companion:
arguments={"skill": "<skill>", "companion": "<name>"}
Behind the gateway a direct ctx_md_render(...) call cannot succeed — lean-ctx holds
no lean-md code. The failure reads like a dead gateway; it is a misaddressed call.
(Wired straight into your MCP client instead — lean-md mcp as its own server —
lean-md exposes ctx_md_render as a plain direct tool; then call it bare. Step 1
below tells you which topology you are in.)
Diagnosis order
ctx_tools(action="list")— does it showlean-md [stdio, enabled]? Then you are behind the gateway, everything works, and the call was merely misaddressed. Fix the call, do not fall back. (No lean-ctx gateway at all, butctx_md_rendersits in your own tool list? Direct topology — the bare call is correct.)Transport closed? Retry once — sporadic, the gateway respawns the server.- Only if the server is genuinely absent: shell fallback (below).
Shell fallback (absent server only)
Read lean_md_bin and lean_md_skills_dir from .lean-ctx/lean-md/vars.toml,
export LEAN_MD_SKILLS_DIR=<lean_md_skills_dir>, then run
<lean_md_bin> render --skill <skill> --phase <phase> --consumer=ai.
Without lean_md_skills_dir the binary reports PACK_MISSING. Same binary,
byte-identical output.
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.
- 8d ago First seen · 47 lines · 45 tokens per session scan A 40f80db0376e
lmd-rendering-skills is a skill published in the GitHub repository dasTholo/lean-md (5 stars, last pushed 8d ago), licensed Apache-2.0. It adds 45 tokens to every session and 558 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…