Token Efficient Markdown

Token-Efficient Markdown Protocol (Structural Density Standard)

Overview

When generating technical documentation, architectural RFCs, or PR reviews in markdown, default LLM responses often output decorative formatting:

• Padded table columns with 40 spaces per cell to make raw text align visually
• Decorative ASCII horizontal dividers (================================)
• Triple newlines between small paragraphs
• Long repetitive subtitle sentences under every heading

In a 500-line markdown artifact, decorative formatting consumes 800 to 1,200 redundant tokens without adding any semantic value to rendered HTML viewports.

The Token-Efficient Markdown Protocol enforces high-density structural formatting, preserving perfect HTML rendering while eliminating formatting bloat.

Verbose Decorative Markdown vs. Token-Efficient High Density

┌─────────────────────────────────────────────────────────────┐
│                 Markdown Token Density Impact               │
│                                                             │
│  Verbose Decorative Markdown (120 Tokens):                  │
│  ========================================================   │
│  ### Database Configuration Details                         │
│  In this section we provide the details for the database.   │
│                                                             │
│  | Parameter Name         | Type        | Default Value   | │
│  | :--------------------- | :---------- | :-------------- | │
│  | max_connections        | integer     | 100             | │
│  ========================================================   │
│                                                             │
│  Token-Efficient Markdown (35 Tokens - 70.8% Cut!):         │
│  ### Database Configuration                                 │
│  | Parameter | Type | Default |                             │
│  | :--- | :--- | :--- |                                     │
│  | max_connections | int | 100 |                             │
│  ↳ 35 clean tokens, renders identically in all browsers!    │
└─────────────────────────────────────────────────────────────┘

The 4 Rules of High-Density Markdown

1. Zero Space-Padded Table Pipes

Markdown renderers (GitHub, VS Code, Browser) dynamically size table columns. Never pad spaces to force alignment in raw text:

<!-- ❌ Anti-Pattern (45 Tokens): -->
| Column A              | Column B              |
| :-------------------- | :-------------------- |
| Value 1               | Value 2               |

<!-- 🟢 High Density (16 Tokens): -->
| Column A | Column B |
| :--- | :--- |
| Value 1 | Value 2 |

2. Single-Line Spacing Max

Never output more than a single empty line between paragraphs or sections. Collapse \n\n\n to \n\n.

3. Omit Decorative ASCII Banners

Never emit ========== or ~~~~~~~~~~ dividers. If a visual divider is required, use standard ---.

4. Direct Headings Without Narrative Subtitles

Never write introductory fluff sentences below headings ("In this section below, you will find..."). Let the heading lead directly into the technical table, code block, or bullet list.

Benchmark Comparison

Generating a comprehensive 10-section Architecture RFC document:

Agent Operational Directive

MANDATORY: Agents generating markdown artifacts or tables must use compact pipe delimiters (| Col | Col |), collapse consecutive blank lines, and eliminate decorative ASCII borders.