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/vibestackdev/vibe-stackWrote 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/vibestackdev/vibe-stack/context-management)<a href="https://agentmods.dev/rules/vibestackdev/vibe-stack/context-management"><img src="https://agentmods.dev/badge/rules/vibestackdev/vibe-stack/context-management/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/vibestackdev/vibe-stack/context-management"><img src="https://agentmods.dev/badge/rules/vibestackdev/vibe-stack/context-management.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.00000 | $0.00454 |
| Opus 5.5 | $0.00000 | $0.00182 |
| Sonnet 5.5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
context-management 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
Context Management Rules
RULE 1: Break Large Tasks Into Sub-Tasks
If a feature requires changes to more than 4 files, break it into sequential sub-tasks. Complete and verify each sub-task before starting the next.
Example — "Add a blog feature with CRUD":
- Sub-task 1: Database migration + RLS policies
- Sub-task 2: Server Actions (create, read, update, delete)
- Sub-task 3: UI components (list, detail, form)
- Sub-task 4: Route handlers + API endpoints
- Sub-task 5: Integration testing
RULE 2: Summarize Before Continuing
If the conversation has been going for more than 5 turns, summarize what has been done and what remains before generating more code.
Template:
Before continuing, let me summarize:
✅ Completed: [list of completed items]
🔄 In progress: [current item]
📋 Remaining: [list of remaining items]
RULE 3: Reference Files By Full Path
When discussing code, ALWAYS use the full path relative to the project root. This prevents confusion between similarly named files.
✅ CORRECT: "Update src/app/dashboard/page.tsx"
❌ WRONG: "Update the dashboard page"
✅ CORRECT: "Import from @/lib/supabase/server"
❌ WRONG: "Import the Supabase client"
RULE 4: One Concern Per Message
Each AI message should address ONE concern clearly:
- ONE file modification with before/after
- ONE bug fix with explanation
- ONE new feature with complete implementation
Do NOT mix unrelated changes in a single response. This makes review harder and increases the chance of introducing bugs.
RULE 5: Keep Rule Files Under 150 Lines
Individual .mdc rule files should stay under 150 lines.
If a rule file grows beyond that, split it into focused sub-rules.
This mirrors the principle from production AI harnesses: keep the index lightweight, put details in separate files.
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 · 62 lines · 0 tokens per session scan A 77cd9736ab59
context-management is a cursor rule published in the GitHub repository vibestackdev/vibe-stack (8 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 454 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.
Other cursor rules, from other repositories
components
React component, styling, theme, accessibility, and RTL instructions.
vibe-tools
Global Rule. This rule should ALWAYS be loaded.
multi-zone-architecture
Multi-zone architecture allows Shipkit applications to be split into multiple Next.js applications while appearing as a single domain to users. This pattern is ideal for.
database-patterns
Use the createTable function with consistent naming.
documentation-system
The Shipkit documentation system uses dynamic file-based loading from the /docs directory at the project root. It supports both .mdx and .md files with full production-ready security features.
local-storage-patterns
Shipkit uses browser local storage as a fallback when no database is configured. This provides a zero-config development experience while maintaining feature parity with database mode.