button-loading

A set of rules for showing progress inside buttons during asynchronous work, meaning an action that continues after the click. Buttons use a spinner and change labels such as “Delete” to “Deleting…”.

In plain words
What is it for?
Use it for buttons that submit, delete, upload, re-index, or otherwise wait for background work to finish. Page loads use skeletons instead.
Why use it?
It makes it clear that an action is still running and helps prevent confusion or repeated clicks.

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/button-loading
Clone the repo
git clone --depth 1 https://github.com/azacdev/knowledge-agent-template

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 183 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00183
Opus 5 $0.00000 $0.00092
Sonnet 5 $0.00000 $0.00037
Haiku 4.5 $0.00000 $0.00018

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

Security

Grade A, and why

button-loading 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/button-loading.mdc · 21 lines

What it actually says

Button loading

When a Button performs async work:

  1. Pass loading={true} on the shared Button from @/components/ui/button.
  2. Change the label to a progressive form ending in an ellipsis:
    • Log in → Logging in…
    • Delete → Deleting…
    • Add document → Adding…
    • Re-index → Re-indexing…
  3. Do not hand-roll a separate spinner — loading prepends Lucide Loader2Icon with animate-spin.
  4. Do not use loading with asChild (links); keep those non-loading.

Page/section loads still use layout skeletons (see loading-skeletons.mdc), not button spinners.

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 · 21 lines · 183 tokens per session scan A b2bac47989ab

Subscribe to this mod's changes

button-loading is a cursor rule published in the GitHub repository azacdev/knowledge-agent-template (2 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 183 tokens. 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.