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 Mertcikla/tld --skill create-diagramgit clone --depth 1 https://github.com/Mertcikla/tldWrote 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/mertcikla/tld/create-diagram)<a href="https://agentmods.dev/skills/mertcikla/tld/create-diagram"><img src="https://agentmods.dev/badge/skills/mertcikla/tld/create-diagram/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/mertcikla/tld/create-diagram"><img src="https://agentmods.dev/badge/skills/mertcikla/tld/create-diagram.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.00057 | $0.01190 |
| Opus 5.5 | $0.00023 | $0.00476 |
| Sonnet 5.5 | $0.00011 | $0.00238 |
| Haiku 4.5 | $0.00006 | $0.00119 |
Grade A, and why
create-diagram 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 10d 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.
Create and Maintain Diagrams
Create a navigable architecture map that answers the user's questions. Keep useful existing content and stable refs when revising it.
Scope and evidence
Read the relevant source and inventory responsibilities, execution/data paths, callers, and dependencies. Connectors must have source evidence or support from the user's system description. Put source anchors in element links (file_path: path#symbol or a folder) and useful evidence in connector descriptions. Distinguish inferred relationships from confirmed behavior.
Choose overview and drill-down boundaries by responsibility. Keep each view readable, usually around 8–12 components. Avoid mirroring directories or expanding every class unless the requested questions need it. Do not add relationships just to eliminate warnings.
Select the destination
Reuse the current workspace or run tld init <project-dir> to create <project-dir>/.tld. Use tld context --format json to confirm the workspace and destination. Pin --workspace, --target, and any --data-dir consistently on previews, writes, and verification; use --target local for a local diagram.
For existing diagrams, inspect tld list views --tree, relevant elements/connectors, and tld inspect <ref> --format json before changing them. Use --source live for current target state. Prefer CLI mutations over editing cached YAML; apply deliberate YAML edits with tld sync.
Author by intent
Use command help for accepted fields and examples, tld import --schema for the exact offline document shape, and JSON output for returned refs/IDs.
- Create a view for an existing element:
tld view create runtime --name "Runtime". Create its owner withtld addfirst; adding children also creates the owner's view automatically. - Add or update a component:
tld add "API" --ref api --parent runtime --kind service --link path#symbol. - Connect components:
tld connect --view runtime --from api --to db --label "reads and writes". This creates the relationship without changing endpoint placements. - Show an unconnected component:
tld view place runtime api.--from <old-view>moves its placement. Sharing may copy existing relationships; inspect live connectors afterward before adding or removing any. - Change metadata or a relationship:
tld update element api description "Handles requests"ortld update connector <listed-key-or-id> label "queries".
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.
- 10d ago Changed · -44 lines · +9 tokens per session ab596de74e9b
- 12d ago Changed · +2 lines 2b9292844815
- 1mo ago Changed · -13 lines 28ea4e379bd9
- 1mo ago Changed · -7 lines 2b9c5825c48c
- 1mo ago First seen · 134 lines · 48 tokens per session scan A 64367fe90de7
create-diagram is a skill published in the GitHub repository Mertcikla/tld (294 stars, last pushed yesterday), licensed Apache-2.0. It adds 57 tokens to every session and 1,190 once invoked, about $0.0002 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
mermaid-skill
A tool for creating text-based Mermaid diagrams and exporting them as PNG, SVG, or PDF files. Mermaid is a format where diagram structure is written as text and laid out automatically.
tldraw-skill
Use when user requests diagrams, flowcharts, architecture charts, or visualizations. Also use proactively when explaining systems with 3+ components, complex data flows, or relationships that benefit from visual representation. Generates .tldr JSON files and exports to PNG/SVG locally using @kitschpatrol/tldraw-cli.
design-system-specification
Design a production-ready Design System and UI/UX visual style guide. Covers design tokens (colors, typography, spacing, shadows, radius), components (buttons, inputs, cards, tables, modals, navigation), layouts, interaction/hover states, iconography, motion design, responsive behavior, accessibility (WCAG 2.2), and…
ux-flow-specification
Document the complete user experience of a product - information architecture, user journeys, screen-by-screen flows, and every UI state (loading, empty, error, success) - independent of visual styling. Use to define exactly how a user moves through a product before or alongside implementation, so navigation and…
redesign-templates
Redesign the resume and cover letter templates into your own house style. Changes typography, palette, and layout while holding the ATS constraints fixed, then proves the result still compiles and still extracts. Run any time; not a pipeline stage.
icon-composer-app-icon-workflow
Design, preview, validate, and integrate Apple app icons with Icon Composer. Use when a task mentions Icon Composer, .icon documents, Liquid Glass app icons, ictool preview exports, app icon design for iOS, iPadOS, macOS, or watchOS, or guided Icon Composer GUI work through Computer Use.