loading-skeletons

A set of interface rules for showing loading states with skeletons: placeholder shapes that match the content about to appear. It requires layout-matching placeholders for page and section loads instead of a lone spinner or “Loading…” message.

In plain words
What is it for?
Use it when designing document lists, cards, messages, or other fetched content, while keeping already-available controls visible.
Why use it?
It keeps the page structure visible while data loads and prevents loading screens from shifting or hiding the real layout.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/azacdev/knowledge-agent-template/loading-skeletons
Clone the repo
git clone --depth 1 https://github.com/azacdev/knowledge-agent-template

Made for: Cursor.

Per session 293 This file is loaded in full into every session.
When invoked 293 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00293 $0.00293
Opus 5 $0.00147 $0.00147
Sonnet 5 $0.00059 $0.00059
Haiku 4.5 $0.00029 $0.00029

Measured yesterday against content hash d28e5e305bbe, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

loading-skeletons 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 yesterday.

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.

.cursor/rules/loading-skeletons.mdc · 19 lines

What it actually says

Loading skeletons

For any loading / pending / hydrating state in Knowledge Agent Template:

  1. Use an inline skeleton (Skeleton from @/components/ui/skeleton), never a lone spinner, “Loading…”, or centered status text for section/page loads.
  2. Match the layout of the section that will appear — same container width, gaps, borders, rounded corners, and approximate block sizes (title line, meta lines, list rows, cards, message bubbles).
  3. Prefer a small colocated *Skeleton next to the real UI (or a fragment in the same file) so the skeleton stays in sync when the layout changes.
  4. Keep real chrome visible when it does not depend on the fetch (page title, search input, back link) and skeleton only the data region.
  5. Button / icon busy on an already-visible control (e.g. re-index, attach upload) may keep a small spinner on that control. Do not replace the whole page with a spinner for that.

Incorrect: spinner + “Loading…” replacing a document list.
Correct: bordered list of 4–6 row skeletons with title / source / meta lines like the real rows.

Changes

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.

  1. yesterday First seen · 19 lines · 293 tokens per session scan A d28e5e305bbe

Subscribe to this mod's changes

loading-skeletons is a cursor rule published in the GitHub repository azacdev/knowledge-agent-template (2 stars, last pushed 6d ago), licensed MIT. It adds 293 tokens to every session, about $0.0015 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.