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/kfnzero/mantis-mcp-server/context-minimal-modegit clone --depth 1 https://github.com/kfnzero/mantis-mcp-serverWhat 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.00992 |
| Opus 5 | $0.00000 | $0.00496 |
| Sonnet 5 | $0.00000 | $0.00198 |
| Haiku 4.5 | $0.00000 | $0.00099 |
Grade A, and why
context-minimal-mode 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- context-minimal-mode — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MINIMAL MODE: CONTEXT OPTIMIZATION
TL;DR: Use this minimal mode reference when context window space is limited. It contains only essential instructions for each workflow phase.
🚨 CORE WORKFLOW - ONE-LINE ESSENTIALS
- INIT: Check Memory Bank files → State task objective → Create section tracking list
- DOCS: Update Memory Bank files → Include platform-specific information
- PLAN: Create steps with [ ] markers in tasks.md → Include specific deliverables
- IMPL: Use tools when possible → Execute ONE command at a time → Update task status in tasks.md
- REFLECT: Document 4 required sections → Include specific items
- ARCHIVE: Archive with required format → Create cross-links
📋 TEMPLATE: SECTION TRACKING
## Section Progress
[ ] 1. INITIALIZATION
[ ] 2. DOCUMENTATION SETUP
[ ] 3. TASK PLANNING
[ ] 4. IMPLEMENTATION
[ ] 5. REFLECTION
[ ] 6. ARCHIVING
🔄 TEMPLATE: SECTION UPDATE
🔄 SECTION UPDATE:
- COMPLETED: [Section]
- UPDATING TRACKING: ✓
🔄 TEMPLATE: TASK STATUS UPDATE
🔄 TASK UPDATE:
- TASK: [Task]
- STATUS: [X]/[ ]
- UPDATED IN: tasks.md ✓
📝 TOOL USAGE PRIORITIES
Use these preferred tools when available:
list_dir- For listing directory contents (not dir/ls)edit_file- For creating/editing files (not echo/touch)read_file- For examining file contents- Use relative paths directly with tools (no cd needed)
run_terminal_cmd- For terminal commands (ONE AT A TIME)
📝 TEMPLATE: COMMAND EXECUTION
### Command: [Brief Description]
Purpose: [Explanation]
```bash
[command]
Result: [Outcome]
## ⚠️ COMMAND SAFETY (PREVENT CRASHES)
- NEVER chain commands with && or similar
- NEVER use mkdir -p for nested directories
- NPM commands CAN include multiple packages: `npm install react react-dom`
- But NEVER chain npm commands: `cd dir && npm install` WILL CRASH
## 📝 TEMPLATE: REFLECTION FORMAT
REFLECTION
What Went Well
- [Item 1]
- [Item 2]
- [Item 3]
Challenges
- [Item 1]
- [Item 2]
Lessons Learned
- [Item 1]
- [Item 2]
- [Item 3]
Improvements for Next Time
- [Item 1]
- [Item 2]
- [Item 3]
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.
- 2d ago First seen · 162 lines · 992 tokens per session scan A 805b46c24696
context-minimal-mode is a cursor rule published in the GitHub repository kfnzero/mantis-mcp-server (10 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 992 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.