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 agentmods add skills/urmzd/dotfiles/create-llms-txtnpx skills add urmzd/dotfiles --skill create-llms-txtgit clone --depth 1 https://github.com/urmzd/dotfilesWrote 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/urmzd/dotfiles/create-llms-txt)<a href="https://agentmods.dev/skills/urmzd/dotfiles/create-llms-txt"><img src="https://agentmods.dev/badge/skills/urmzd/dotfiles/create-llms-txt.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.00068 | $0.01258 |
| Opus 5 | $0.00034 | $0.00629 |
| Sonnet 5 | $0.00014 | $0.00252 |
| Haiku 4.5 | $0.00007 | $0.00126 |
Grade A, and why
create-llms-txt 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 5d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create llms.txt
Generate a high-quality, spec-compliant llms.txt that gives LLMs maximum understanding of a project with minimum tokens.
Spec (llmstxt.org)
The file uses markdown with this exact section order:
- H1 (required) project name
- Blockquote (optional) one-paragraph summary with key context
- Prose (optional) additional detail, any markdown except headings
- H2 sections (optional) lists of
[name](url): descriptionlinks ## Optional(special) links that can be skipped for shorter context
No other heading levels allowed. Every list entry must be a markdown hyperlink. Descriptions after : are optional.
# Project Name
> One-paragraph summary covering what it is, who it's for, and key capabilities.
## Docs
- [README](url): Installation, usage, examples
- [API Reference](url): Endpoint documentation
## Optional
- [CONTRIBUTING](url): How to contribute
Procedure
1. Discover project identity
Read these files (skip missing ones):
README.mdname, summary, featuresAGENTS.mdarchitecture, key directoriespackage.json/Cargo.toml/pyproject.toml/go.modname, description, repo URLCHANGELOG.mdexists? link itCONTRIBUTING.mdexists? link in OptionalLICENSEexists? link in Optional
Determine the repo base URL from git remote or manifest. All links must be absolute URLs pointing to the main branch (e.g. https://github.com/{owner}/{repo}/blob/main/{path}).
2. Identify key files
Scan for files that help an LLM understand the project:
- Entry points (
main.go,src/lib.rs,src/index.ts,app.py, etc.) - Public API surface (exported modules, route definitions, CLI entry)
- Config files that define behavior (
Justfile,Makefile,docker-compose.yml,pyproject.toml) - Schema definitions (OpenAPI, GraphQL, DB migrations)
- Skills (
skills/*/SKILL.md)
Limit to 6-10 key files. Prefer files that explain what the project does over internal implementation.
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.
- 5d ago First seen · 121 lines · 68 tokens per session scan A 6d4cb8e5b7e7
create-llms-txt is a skill published in the GitHub repository urmzd/dotfiles (3 stars, last pushed 23d ago), licensed Apache-2.0. It adds 68 tokens to every session and 1,258 once invoked, about $0.0003 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
benchling-integration
Benchling Python SDK and REST API integration for registry entities, inventory, ELN entries, workflows, Benchling Apps, and Data Warehouse queries. Use when automating lab data with benchling-sdk or the v2 API.
scan-commit
Automatically scan the repository for unstaged/untracked changes, group them into logical commits using hunk-level analysis, stage and commit them following Conventional Commits.
astropy
Core Python library for astronomy and astrophysics workflows that need Astropy APIs, including units/quantities, coordinates, FITS I/O, tables, time systems, WCS, and cosmology. Use when implementing or debugging astronomical data analysis code with Astropy.
esm
Comprehensive toolkit for EvolutionaryScale protein language models including ESM3 (generative multimodal design across sequence, structure, and function) and ESM C (efficient embeddings). Use for protein sequence/structure/function tasks, inverse folding, embeddings, variant design, and ESMFold2 structure prediction…
ralph-loop
Ralph Wiggum 迭代开发循环。三阶段工作流（需求→规划→构建），每阶段有 code review + 测试 gate。 触发词：ralph loop、迭代开发、interview me、plan system、build system。.
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes.