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/zackiles/cursor-mcp-manager/with-javascriptgit clone --depth 1 https://github.com/zackiles/cursor-mcp-managerWhat 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.00000 | $0.05913 |
| Opus 5 | $0.00000 | $0.02957 |
| Sonnet 5 | $0.00000 | $0.01183 |
| Haiku 4.5 | $0.00000 | $0.00591 |
Grade A, and why
with-javascript 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.
This is a copy
84% identical to with-javascript — 44 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 447 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CODING STYLE GUIDE, RULES, AND STANDARDS (JAVASCRIPT AND TYPESCRIPT)
Follow the below coding standards, rules, best practices and style guides.
Naming and Casing
- kebab-case: for file names.
- camelCase: for instance names.
- PascalCase: for class and symbol names.
- UPPER_SNAKE_CASE: for constants.
- Consistent: When naming things, always review the naming patterns and conventions of similar this and follow that those
- Evolve Names Over Time: When refactoring previous code, look for opporutnities to rename not only the things you're working on but related things where renaming both would provide an overall better pattern, convention, or abstraction for the broader code base.
Naming Specificity
- Broad or abstracted names for top-level things such as: namespaces, classes, types shared by multiple files, or global conceps and terms.
- Narrow or specific or descriptive names for local or specific things, or when other rules, instructions, or consistency in the codebase requires it.
Renaming and Refactoring Names
- IMPORTANT: Avoid renaming the following unless explicitly asked to: environment or global cinfug variable names, project or package names, import paths, file names, module names.
- After renaming things, find any JSDoc or inline comments that refer to the things that were named and update them to use the new names.
- After renaming things, ensure similar things that are named in a way that is similar to the previous name are also refactored to remain consistent naming patterns, conventions, and abstracions.
- Avoid renaming things in a way that would directly violate any instruction or rule provided to you, or indirectly cause side-effects in the final code that would violate other rules or instructions provided to you.
Code Ordering
When generating, refactoring, or reviewing code files, you will prefer the following ordering of its top-level items:
- Remote Imports
- Local Imports
- Hoisted Variables and References
- Methods
- Exports: should be declared according to the rules and instructions defined in the "### Exports" section.
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.
- yesterday First seen · 447 lines · 5,913 tokens per session scan A 1c4d8133c376
with-javascript is a cursor rule published in the GitHub repository zackiles/cursor-mcp-manager (3 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,913 tokens. A static security scan graded it A with 0 findings. It is 84% identical to with-javascript, differing in 44 lines, and is treated as a copy.
Other cursor rules, from other repositories
1c-coding-standards
Стандарты кода BSL: именование, запросы, коллекции.
1c-skd-two-pass-preprocessing
Двухпроходный СКД: предобработка детальных записей до свертки.
agent-working-memory
Рабочая память агента: файлы плана, передача сессии, журнал инцидентов.
testing-patterns
Паттерны тестирования 1С: YaXUnit, Vanessa.
language-agnostic-patterns
Language-agnostic programming patterns: SOLID, design patterns, clean code, and architecture. Load when refactoring, designing abstractions, or reviewing structure — not for everyday syntax.
cursor-tools-mastery
Cursor 3.7 runtime guide: choose the right tool, canvases, Design Mode, /worktree, /best-of-n, Await, and parallel execution where safe.