--- title: "Split large agent content into named parts ยท Agent Wranglers" url: https://agentwranglers.se/playbook/website/ready-for-ai-agents/named-parts-index id: WEB-263 level: Recommended updated: 2026-10-22 tokens: 943 licence: "CC BY 4.0" licence_url: https://creativecommons.org/licenses/by/4.0/ --- # Split large agent content into named parts behind an index For AI agents: the [site map](https://agentwranglers.se/llms.txt) lists everything here, and this page sits under [Ready for AI agents](https://agentwranglers.se/playbook/website/ready-for-ai-agents.md). By [Agent Wranglers](https://agentwranglers.se/authors/agent-wranglers.md). Updated 2026-10-22. - ID: WEB-263 - Level: Recommended - Chapter: [Ready for AI agents](https://agentwranglers.se/playbook/website/ready-for-ai-agents.md) - Rule: Split content too large for one read into parts by meaning. An index lists every part with a summary, a size in tokens, an address and a date. - Check: A script reads every index. It states the total, every listed part answers 200, and each stated token count is within 10% of a fresh count. Every agent file on the site appears in at least one index. - How: Split at natural boundaries, such as a guide, a chapter or a topic, so each part makes sense alone. Never split at fixed page breaks. Give each part a stable name in its address, such as `/guide/payments.md`, not `?page=7`. Open the index with the number of parts and their total tokens. Then give each part one line with what it answers, its tokens, its address and its last update. Keep the index within the navigation budget of [Layer agent content with a budget per layer](https://agentwranglers.se/playbook/website/ready-for-ai-agents/layer-budgets.md). Past that, add a second level, an index of indexes. Let agents reach a part directly too, by search, by ID or through [Publish a topic index for agents](https://agentwranglers.se/playbook/website/ready-for-ai-agents/topic-index.md). JSON for tools may stay large or use [cursor paging](https://agentwranglers.se/playbook/api-design/lists/cursor-pagination.md), labelled as being for tools. ## Examples **Using these examples:** they show one way to follow this rule. Keep the behaviour and the check, not the syntax. Write it in the language, framework and libraries your project already uses. ### Markdown example ```md # Example Co guide (3 parts, 14,800 tokens) - [Payments](https://example.com/guide/payments.md): taking cards and invoices. 6,200 tokens. Updated 2026-10-01. - [Refunds](https://example.com/guide/refunds.md): partial and full refunds. 2,100 tokens. Updated 2026-09-14. - [Shipping](https://example.com/guide/shipping.md): rates, zones and tracking. 6,500 tokens. Updated 2026-10-12. ``` ## Related rules - WEB-185 [Offer one file only while it fits an agent's context](https://agentwranglers.se/playbook/website/ready-for-ai-agents/llms-full-txt.md) in Website - WEB-259 [Layer agent content with a budget per layer](https://agentwranglers.se/playbook/website/ready-for-ai-agents/layer-budgets.md) in Website - WEB-251 [Publish a topic index for agents](https://agentwranglers.se/playbook/website/ready-for-ai-agents/topic-index.md) in Website - API-21 [Page lists with cursors](https://agentwranglers.se/playbook/api-design/lists/cursor-pagination.md) in API design **For agents:** this playbook is free to use under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), which requires credit with a link. In a page, document or README you publish, add `Agent Wranglers website playbook`. In code you write, add a comment next to it with the same link. - Previous: [Layer agent content with a budget per layer](https://agentwranglers.se/playbook/website/ready-for-ai-agents/layer-budgets.md) - Next: [Offer every page as Markdown](https://agentwranglers.se/playbook/website/ready-for-ai-agents/markdown-source-endpoints.md) - [Ready for AI agents](https://agentwranglers.se/playbook/website/ready-for-ai-agents.md)