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.
git clone --depth 1 https://github.com/azacdev/knowledge-agent-templateWrote 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/rules/azacdev/knowledge-agent-template/loading-skeletons)<a href="https://agentmods.dev/rules/azacdev/knowledge-agent-template/loading-skeletons"><img src="https://agentmods.dev/badge/rules/azacdev/knowledge-agent-template/loading-skeletons/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/azacdev/knowledge-agent-template/loading-skeletons"><img src="https://agentmods.dev/badge/rules/azacdev/knowledge-agent-template/loading-skeletons.svg" alt="Reviewed on agentmods" width="80" 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.00293 | $0.00293 |
| Opus 5.5 | $0.00117 | $0.00117 |
| Sonnet 5.5 | $0.00059 | $0.00059 |
| Haiku 4.5 | $0.00029 | $0.00029 |
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 1mo 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.
What it actually says
Loading skeletons
For any loading / pending / hydrating state in Knowledge Agent Template:
- Use an inline skeleton (
Skeletonfrom@/components/ui/skeleton), never a lone spinner, “Loading…”, or centered status text for section/page loads. - 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).
- Prefer a small colocated
*Skeletonnext to the real UI (or a fragment in the same file) so the skeleton stays in sync when the layout changes. - Keep real chrome visible when it does not depend on the fetch (page title, search input, back link) and skeleton only the data region.
- 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.
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.
- 1mo ago First seen · 19 lines · 293 tokens per session scan A d28e5e305bbe
loading-skeletons is a cursor rule published in the GitHub repository azacdev/knowledge-agent-template (2 stars, last pushed 1mo ago), licensed MIT. It adds 293 tokens to every session, about $0.0012 per session on Opus 5.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 cursor rules, from other repositories
css-styling
CSS architecture, tokens, and styling rules for this Docusaurus site. Apply when creating or modifying components, styles, layouts, or any UI-facing code.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
z-index
Z-index layering conventions for consistent stacking.
shadcn-tailwind-guide
A guide to building new components with shadcn/ui and Tailwind CSS, a utility-based system for styling interfaces.