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/glide-the/im-dreamWrote 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/glide-the/im-dream/vibe-loading)<a href="https://agentmods.dev/rules/glide-the/im-dream/vibe-loading"><img src="https://agentmods.dev/badge/rules/glide-the/im-dream/vibe-loading/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/glide-the/im-dream/vibe-loading"><img src="https://agentmods.dev/badge/rules/glide-the/im-dream/vibe-loading.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.00147 | $0.00147 |
| Opus 5.5 | $0.00059 | $0.00059 |
| Sonnet 5.5 | $0.00029 | $0.00029 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
vibe-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 12d 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
Vibe Loading Rules
Three Layers
- Hot:
CLAUDE.md,today.md - Rules:
.cursor/rules/*.mdc - Heavy:
docs/*.md(on-demand only)
Anti-Bloat
- Never pre-load all heavy docs.
- Keep at most two heavy docs active simultaneously.
- Summarize and release old heavy docs before loading new ones.
- Declare each load action with target and purpose.
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.
- 12d ago First seen · 22 lines · 147 tokens per session scan A 5cc1600ac0ec
vibe-loading is a cursor rule published in the GitHub repository glide-the/im-dream (0 stars, last pushed yesterday), licensed MIT. It adds 147 tokens to every session, about $0.0006 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-10-02.
Other cursor rules, from other repositories
explorer-interface-brief
Use when asked to design the interface for an interactive 3D explorer, plan a UI for exploring a 3D model of a topic, or write an image-model prompt for a 3D learning app mock-up. Produces, from a topic, the UI design brief (audience, layout, panels, interactions, label style, colour palette, accessibility) and an…
reflection-basic
Basic reflection format for Level 2 Simple Enhancement tasks.
simplicity
Simplicity - smallest correct diff; reuse, platform, installed deps before new code; no speculative abstraction.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
feedback-enhanced
Rules for an interactive feedback system that lets users and an AI agent discuss complex development work in real time. It includes guidance for recording decisions, tracking progress and handling detailed inputs such as code and diagrams.
kiss-ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.