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 instructions/polydile/dile-components/agents-mdgit clone --depth 1 https://github.com/Polydile/dile-componentsWhat 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 | $0.00997 | $0.00997 |
| Opus 5 | $0.00498 | $0.00498 |
| Sonnet 5 | $0.00199 | $0.00199 |
| Haiku 4.5 | $0.00100 | $0.00100 |
Grade A, and why
dile-components AGENTS.md 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 2d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Guidelines for Dile Components
Repository overview
This repository is a monorepo for the Dile Components library. It contains multiple packages under the packages/ directory, each focused on a different area of the component ecosystem.
Packages
packages/ui— UI components for graphical interfaces, published as@dile/uipackages/utils— utility components, published as@dile/utilspackages/crud— CRUD-related components, published as@dile/crudpackages/editor— rich text / editor components, published as@dile/editorpackages/icons— icon assets and helpers, published as@dile/iconspackages/iconlib— icon library web component implementationspackages/lib— shared library helpers and app-oriented abstractions
Documentation site
The documentation site project is located in the docs/ directory. This is the source for the Eleventy-based documentation website.
Component doc pages (docs/components/*.md) contain html:preview code blocks that render live demos. These blocks share the same page/global scope (window), so a component's <script type="module">import '@dile/ui/components/<name>/<name>.js';</script> only needs to appear once per page — customElements.define registers the element on window and every later html:preview block on that page can use the tag without importing it again. Only import again if a later block introduces a different component not yet registered.
Demos
Interactive demos are stored in the demos/ directory.
- UI component demos go in
demos/ui/ - Utils component demos go in
demos/utils/ - CRUD component demos go in
demos/crud/
When creating a new component
When implementing a new component, follow these conventions:
- Create the component in the appropriate package folder under
packages/. - Create a demo file in the matching demos folder:
- UI components:
demos/ui/ - Utils components:
demos/utils/ - CRUD components:
demos/crud/
- UI components:
- Create documentation for the component:
- UI components:
docs/components/ - CRUD components:
docs/crud/
- UI components:
- Add the demo to the corresponding demo index file:
- CRUD components:
demos/crud/index.html - Other components:
demos/index.html - Keep the demo list in alphabetical order.
- CRUD components:
- Use the existing component documentation files as a base for style and structure.
- Follow the naming and file organization patterns already used by existing components in the repository.
- Keep the documentation concise, practical, and aligned with the existing docs format.
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.
- 2d ago First seen · 68 lines · 997 tokens per session scan A f810ac25341c
dile-components AGENTS.md is an instructions file published in the GitHub repository Polydile/dile-components (106 stars, last pushed 2d ago), licensed MIT. It adds 997 tokens to every session, about $0.0050 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-30.
Other instructions, from other repositories
uview-plus AGENTS.md
AGENTS.md instructions for ijry/uview-plus, covering agents, 提交规范, 发布规范 and uview-plus说明.
mcp-ui copilot-instructions.md
Copilot instructions for MCP-UI-Org/mcp-ui, covering mcp-ui development instructions, working effectively, bootstrap and build (critical - set 60+ minute timeouts), testing (critical - set 30+ minute timeouts) and code quality (always run before committing).
tool-ui CLAUDE.md
Instructions for assistant-ui/tool-ui, covering tool ui, commands, tooling, stack and architecture.
tool-ui AGENTS.md
Instructions for assistant-ui/tool-ui, covering agents.md, cursor cloud specific instructions, project overview, running services and commands reference.
OpenClaw-Admin AGENTS.md
Instructions for itq5/OpenClaw-Admin, covering 仓库协作指南, 项目结构与模块组织, 构建、测试与开发命令, 代码风格与命名规范 and 测试要求.
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.