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/archive)<a href="https://agentmods.dev/rules/kfnzero/mantis-mcp-server/archive"><img src="https://agentmods.dev/badge/rules/kfnzero/mantis-mcp-server/archive/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/archive"><img src="https://agentmods.dev/badge/rules/kfnzero/mantis-mcp-server/archive.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.00602 | $0.00602 |
| Opus 5.5 | $0.00241 | $0.00241 |
| Sonnet 5.5 | $0.00120 | $0.00120 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
archive 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:
- archive — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TASK ARCHIVING PROTOCOL
TL;DR: After completing a task, archive it in completed_tasks.md with Implementation Results, Completed Testing, Lessons Learned, and Documentation Updates sections. Cross-link in progress.md and activeContext.md.
📁 ARCHIVE SETUP
At project start:
- Create
docs/archive/directory - Create
completed_tasks.mdwith only this header:# Completed Tasks - Don't add placeholder text like "No tasks completed yet"
📋 ARCHIVE FORMAT
For each completed task, use this exact format:
## Task: [Task Name] (v1.0)
Last Updated: YYYY-MM-DD
### Implementation Results
[What was implemented]
### Completed Testing
[How it was tested]
### Lessons Learned
[Key insights gained]
### Documentation Updates
[Memory Bank files updated]
See examples: archive-examples.mdc
🔄 CROSS-LINKING
After archiving, create these cross-links:
In progress.md:
## Completed Tasks
- [Task Name] - Completed on YYYY-MM-DD, see [archive entry](mdc:../docs/archive/completed_tasks.md#task-task-name-v10)
In activeContext.md:
## Recent Completions
- [Task Name] has been completed and archived. Next focus is on [Next Task].
✅ ARCHIVE CHECKLIST
Verify these items for every archive:
- docs/archive directory exists
- completed_tasks.md exists with proper header
- Archive entry includes:
- Task name with (v1.0) version
- Date in YYYY-MM-DD format
- All four required sections
- No placeholder text remains
- progress.md updated with archive link
- activeContext.md updated with completion note
🔍 SECTION REQUIREMENTS
-
Implementation Results
- List specific features implemented
- Note any deviations from original plan
- Mention technologies used
-
Completed Testing
- Describe testing methods used
- Note test results and coverage
- Mention any edge cases tested
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 · 96 lines · 602 tokens per session scan A 25ae96ddb1fb
archive is a cursor rule published in the GitHub repository kfnzero/mantis-mcp-server (12 stars, last pushed 1y ago), licensed MIT. It adds 602 tokens to every session, about $0.0024 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
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).
sprint-planning
BMAD BMM Agent: sprint-planning.