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.
npx agentmods add rules/kok-o/koko-contextos-agents/context-managergit clone --depth 1 https://github.com/kok-o/koko-contextos-agentsWrote 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/kok-o/koko-contextos-agents/context-manager)<a href="https://agentmods.dev/rules/kok-o/koko-contextos-agents/context-manager"><img src="https://agentmods.dev/badge/rules/kok-o/koko-contextos-agents/context-manager.svg" alt="Measured on agentmods" 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 | $0.00006 | $0.00656 |
| Opus 5 | $0.00003 | $0.00328 |
| Sonnet 5 | $0.00001 | $0.00131 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade A, and why
context-manager 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: context-manager
context-manager
Overview
A brief summary of what the skill does and its core philosophy.
When to Use
Context for when this skill is applicable.
Rules & Patterns
You are the Context Manager. Your job is to prevent context overload.
How It Works
When given a task:
Step 1: Classify the task
task:
type: [frontend | backend | fullstack | architecture | bugfix | refactor | deploy | review]
scope: [module | feature | file | project-wide]
module: {{module_name from Project Graph}}
Step 2: Consult the Project Graph
If docs/PROJECT_GRAPH.md exists:
- Find the module this task belongs to
- Get the module's dependencies
- Get the module's required skills
- Get the files this task will likely touch
Step 3: Apply Context Rules
Load references/context-rules.md and apply the task type → document mapping.
Step 4: Return Context Package
Output a context package:
context:
documents:
required:
- docs/API.md # sections: [appointments]
- docs/ARCHITECTURE.md # sections: [backend, api-layer]
optional:
- docs/decisions/0003-postgres.md
skipped:
- docs/UI.md # reason: backend task
- docs/DATABASE.md # reason: no schema change
skills:
loaded: [typescript, node, postgres, testing]
skipped: [react, tailwind] # reason: backend task
project_graph:
module: appointments
dependencies: [auth, patients]
affected_files:
- src/modules/appointments/api/**
- src/modules/appointments/services/**
Step 5: Validate Budget
Check total token count. If over budget (see context-rules.md):
- Trim Level 1 docs to summaries
- Load only affected sections of Level 2 docs
- Keep Level 3 (skills) at full detail
Context Caching
After first compilation for a module, cache the result:
.cache/
frontend.context.yaml
backend.context.yaml
appointments.context.yaml
Invalidate cache when:
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.
- 4d ago First seen · 128 lines · 6 tokens per session scan A 3c510b24915f
context-manager is a cursor rule published in the GitHub repository kok-o/koko-contextos-agents (2 stars, last pushed 4d ago), licensed MIT. It adds 6 tokens to every session and 656 once invoked, about $0.0000 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.
Other cursor rules, from other repositories
react-composition-patterns
React composition patterns for scalable component architecture including compound components, context providers, state management, boolean prop alternatives, render props vs children, and React 19 API changes. Use when refactoring components with many boolean props, building component libraries, designing flexible…
react-rerender-optimization
React re-render optimization patterns including memo, useMemo, useCallback, useState, useRef, and derived state. Use when components re-render too often, dealing with stale closures, dependency arrays, performance issues, or optimizing slow components.
index
This project uses Unity 6.2 (LTS 2025) with modern systems and architectural approaches.
general-typescript-rule
Applies general TypeScript best practices and style guidelines to all TypeScript files in the project.
readme-best-practices
README Best Practices - enforces high-quality README patterns when creating or editing README files.
pull-request-changelist-instructions
Guidelines for creating consistent pull request changelists in markdown format with proper code block formatting.