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 infraspecdev/tesseract --skill lld-docsgit clone --depth 1 https://github.com/infraspecdev/tesseractWrote 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/infraspecdev/tesseract/lld-docs)<a href="https://agentmods.dev/skills/infraspecdev/tesseract/lld-docs"><img src="https://agentmods.dev/badge/skills/infraspecdev/tesseract/lld-docs/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/infraspecdev/tesseract/lld-docs"><img src="https://agentmods.dev/badge/skills/infraspecdev/tesseract/lld-docs.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.00093 | $0.01871 |
| Opus 5.5 | $0.00037 | $0.00748 |
| Sonnet 5.5 | $0.00019 | $0.00374 |
| Haiku 4.5 | $0.00009 | $0.00187 |
Grade A, and why
lld-docs 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
lld-docs
Author component-scoped Low-Level Design documents in one of two operational modes:
draft— net-new component. Emit a fresh template (backend or infra per the resolvedtype), populate sections from the available context (PRD, research, TRD, repo evidence), and atomic-write to the target path.merge— enhancement of an existing canonical LLD. The caller has already copieddocs/lld/<component>.mdinto the target draft path; this skill identifies which sections the current work affects, edits those sections in the draft, and leaves untouched sections verbatim.
Both modes preserve all 14 sections in canonical order (per
shield/schema/lld-sections-<type>.yaml) and emit explicit {#kebab-case}
anchors. The shared header metadata block precedes §1; the §14 Changelog row
is the only mandatory addition on merge runs.
Template selection
type argument |
Slug allow-list | Section template |
|---|---|---|
backend |
shield/schema/lld-sections-backend.yaml |
lld-template-backend.md |
infra |
shield/schema/lld-sections-infra.yaml |
lld-template-infra.md |
type is required. It's resolved by the caller (the /lld command or /plan)
before invoking this skill.
Output paths
| Caller | Target path |
|---|---|
/lld <component> (Path A) |
docs/lld/<component>.md (canonical, direct) |
/plan TRD-driven (Path B, M2 plan) |
docs/shield/<feature>/lld-<component>.md (draft) |
This skill does NOT promote drafts to the canonical path — that's /implement's
job at milestone close (M2 plan, step 5h).
Atomic write contract
- Compute the target path.
- Write content to
<target>.tmp. - Atomic-rename
<target>.tmp→<target>viaos.replace()(Python) ormv(shell). - On any failure between steps 2 and 3 (write error, signal interrupt),
remove
<target>.tmpand surface the error. Never leave a partial<target>behind. - Before the write, apply
shield:writing-styleto author-written prose sections (overview, rationale, narrative). Do NOT alter the provenance stamp, the §14 Changelog rows, header metadata, code blocks, orn/a — <reason>escapes.
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 · 171 lines · 93 tokens per session scan A 453b2e7236f2
lld-docs is a skill published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 93 tokens to every session and 1,871 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…