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 skills add navendubrajesh/context-management-for-agents --skill cursor-customizationgit clone --depth 1 https://github.com/navendubrajesh/context-management-for-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/skills/navendubrajesh/context-management-for-agents/cursor-customization)<a href="https://agentmods.dev/skills/navendubrajesh/context-management-for-agents/cursor-customization"><img src="https://agentmods.dev/badge/skills/navendubrajesh/context-management-for-agents/cursor-customization/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/skills/navendubrajesh/context-management-for-agents/cursor-customization"><img src="https://agentmods.dev/badge/skills/navendubrajesh/context-management-for-agents/cursor-customization.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.00089 | $0.01207 |
| Opus 5 | $0.00044 | $0.00603 |
| Sonnet 5 | $0.00018 | $0.00241 |
| Haiku 4.5 | $0.00009 | $0.00121 |
Grade A, and why
cursor-customization 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 10d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Customization
Cursor exposes a layered steering surface: Project Rules (.cursor/rules/*.mdc), User Rules, Team Rules, AGENTS.md, and MCP servers. These files are the primary user-controlled context channel for Agent (Chat). This skill covers authoring them with correct activation modes and token budgeting.
When to Activate
Activate this skill when:
- Creating or restructuring
.cursor/rules/or root/nestedAGENTS.md - Choosing between Always Apply, glob-scoped, agent-requested, and manual rule modes
- Agent ignores stated conventions or applies backend rules to frontend files
- Responses degrade after rules grow ("rule bloat")
- Configuring MCP servers and deciding which to enable for Agent
Do not activate this skill for adjacent work owned by other skills:
- Do not activate for semantic indexing or @-mention mechanics:
cursor-context-architecture. - Do not activate for compression and session lifecycle:
cursor-session-management. - Do not activate for platform-agnostic instruction theory:
context-fundamentals. - Do not activate for MCP tool schema design:
tool-design.
Core Concepts
Project rules (.mdc)
Rules live in .cursor/rules/ as .mdc files with YAML frontmatter: description, globs, alwaysApply. Plain .md files in that directory are ignored — use .mdc or AGENTS.md instead.
| Mode | Frontmatter pattern | When it loads |
|---|---|---|
| Always Apply | alwaysApply: true |
Every Agent session |
| Glob-scoped | globs: "src/**/*.tsx", alwaysApply: false |
Matching files in context |
| Agent-requested | description: "...", no globs |
Agent decides from description |
| Manual | no description, no globs | @rule-name in chat |
Precedence on conflict: Team Rules → Project Rules → User Rules.
Token budgeting always-on rules
alwaysApply: true rules prepend to every Agent request. Keep universal rules under ~50 lines of behavior-changing content. Push domain-specific guidance to glob-scoped or agent-requested rules — progressive disclosure native to Cursor.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 91 lines · 89 tokens per session scan A cc7aafacfdb0
cursor-customization is a skill published in the GitHub repository navendubrajesh/context-management-for-agents (2 stars, last pushed 2mo ago), licensed MIT. It adds 89 tokens to every session and 1,207 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…