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/kfnzero/mantis-mcp-serverWrote 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/kfnzero/mantis-mcp-server/van-protocol)<a href="https://agentmods.dev/rules/kfnzero/mantis-mcp-server/van-protocol"><img src="https://agentmods.dev/badge/rules/kfnzero/mantis-mcp-server/van-protocol/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/kfnzero/mantis-mcp-server/van-protocol"><img src="https://agentmods.dev/badge/rules/kfnzero/mantis-mcp-server/van-protocol.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.02023 | $0.02023 |
| Opus 5.5 | $0.00809 | $0.00809 |
| Sonnet 5.5 | $0.00405 | $0.00405 |
| Haiku 4.5 | $0.00202 | $0.00202 |
Grade A, and why
van-protocol 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- van-protocol — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADAPTIVE VAN PROTOCOL
TL;DR: When user types "VAN", respond with "OK VAN", determine task complexity level, and adapt the workflow process accordingly. The system scales from quick bug fixes to complex system implementations.
🚀 QUICK START RESPONSE
When the user types ONLY "VAN", immediately respond:
OK VAN
I'll determine the appropriate process level based on the task complexity:
## COMPLEXITY ANALYSIS
[ ] Analyzing task type and complexity...
[ ] Determining appropriate process level...
## FILE VERIFICATION
[ ] .cursorrules
[ ] memory-bank directory
[ ] docs/archive directory
[ ] tasks.md
Checking these now...
📋 TASK COMPLEXITY DETERMINATION
Analyze the task to determine the appropriate complexity level:
Level 1: Quick Bug Fix
- Keywords: "fix", "broken", "not working", "issue", "bug", "error"
- Scope: Single component or simple UI element
- Purpose: Restore existing functionality
- Examples: "Fix login button", "Fix styling issue", "Fix validation error"
Level 2: Simple Enhancement
- Keywords: "add", "improve", "update", "change", "enhance"
- Scope: Single component or subsystem
- Purpose: Small feature addition or enhancement
- Examples: "Add logout button", "Improve form validation", "Update header style"
Level 3: Intermediate Feature
- Keywords: "implement", "create", "develop", "build"
- Scope: Complete feature requiring multiple components
- Purpose: Significant new functionality
- Examples: "Implement user profiles", "Create dashboard", "Develop search functionality"
Level 4: Complex System
- Keywords: "system", "architecture", "redesign", "integration", "framework"
- Scope: Multiple subsystems or entire application
- Purpose: Major architectural changes
- Examples: "Implement authentication system", "Build payment processing", "Create microservice architecture"
📋 FILE VERIFICATION PROCESS
Check for critical files and create them if missing:
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 · 307 lines · 2,023 tokens per session scan A b29bbb02a3af
van-protocol is a cursor rule published in the GitHub repository kfnzero/mantis-mcp-server (12 stars, last pushed 1y ago), licensed MIT. It adds 2,023 tokens to every session, about $0.0081 per session on Opus 5.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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).