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/creative-phase-metricsgit 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.02163 |
| Opus 5 | $0.00000 | $0.01081 |
| Sonnet 5 | $0.00000 | $0.00433 |
| Haiku 4.5 | $0.00000 | $0.00216 |
Grade A, and why
creative-phase-metrics 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 3d 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:
- creative-phase-metrics — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CREATIVE PHASE METRICS
TL;DR: This file establishes objective evaluation frameworks and quality metrics for creative phase outputs. It provides structured approaches to evaluate design decisions, weighted decision matrices for option comparison, and verification metrics to ensure solutions meet requirements.
📊 QUALITY EVALUATION FRAMEWORK
Evaluate creative phase outputs using these objective criteria:
1. Decision Quality Metrics
📊 DECISION QUALITY SCORE
- Requirement Coverage: [1-5] - How completely does the solution address requirements?
- Option Exploration: [1-5] - How thoroughly were alternatives explored?
- Trade-off Analysis: [1-5] - How well were pros/cons evaluated?
- Verification Rigor: [1-5] - How systematically was the solution verified?
- Implementation Guidance: [1-5] - How clear is the implementation path?
TOTAL SCORE: [5-25]
- 20-25: Excellent - Comprehensive analysis with strong justification
- 15-19: Good - Solid analysis with adequate justification
- 10-14: Satisfactory - Basic analysis with minimal justification
- 5-9: Needs Improvement - Incomplete analysis, inadequate justification
→ Minimum acceptable score: 15
⚖️ WEIGHTED DECISION MATRIX
For evaluating multiple options against weighted criteria:
⚖️ WEIGHTED DECISION MATRIX
| Criteria | Weight | Option 1 | Score 1 | Option 2 | Score 2 | Option 3 | Score 3 |
|----------|--------|----------|---------|----------|---------|----------|---------|
| Criterion 1 | [1-5] | Rating [1-10] | Weight × Rating | Rating [1-10] | Weight × Rating | Rating [1-10] | Weight × Rating |
| Criterion 2 | [1-5] | Rating [1-10] | Weight × Rating | Rating [1-10] | Weight × Rating | Rating [1-10] | Weight × Rating |
| Criterion 3 | [1-5] | Rating [1-10] | Weight × Rating | Rating [1-10] | Weight × Rating | Rating [1-10] | Weight × Rating |
| Totals | | | Sum | | Sum | | Sum |
→ Highest total score indicates the recommended option
→ Document rationale for weights and ratings
🔍 VERIFICATION METRICS
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.
- 3d ago First seen · 277 lines · 2,163 tokens per session scan A 27afddbff183
creative-phase-metrics 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 2,163 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.