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/SwonVIP/mcp-server-talkWrote 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/swonvip/mcp-server-talk/presentation-review-checklist)<a href="https://agentmods.dev/rules/swonvip/mcp-server-talk/presentation-review-checklist"><img src="https://agentmods.dev/badge/rules/swonvip/mcp-server-talk/presentation-review-checklist.svg" alt="Measured on agentmods" 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.00000 | $0.00905 |
| Opus 5 | $0.00000 | $0.00452 |
| Sonnet 5 | $0.00000 | $0.00181 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
presentation-review-checklist 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Server Presentation Review Checklist
Content Review
Content Density (Updated)
- Slide 1 (Introduction): Good balance of content
- Slide 2 (Toolbox Analogy): Good balance with vertical slide split
- Slide 3 (Computer Interface Evolution): Two-column layout helps
- Slide 4 (USB-C Analogy): Good balance with visual elements
- Slide 5a (Core Architecture - Overview): Good focus on high-level concepts
- Slide 5b (Core Architecture - Components): Well organized with two-column layout
- Slide 6 (Capabilities): Well split across vertical slides
- Slide 7a (Communication Flow - Overview): Focused on key concepts
- Slide 7b (Communication Flow - Steps): Better organized with two-column layout
- Slide 8 (Implementation): Good balance with code example
- Slide 9 (Security Part 1): Good balance
- Slide 10 (Security Part 2): Good balance
- Slide 11a (Best Practices - Security): Focused content
- Slide 11b (Best Practices - Implementation): Well-structured with new points
- Slide 12 (Use Cases): Well structured with stacked fragments
- Slide 13 (Future): Good balance
- Slide 14 (Conclusion): Good balance
Original Splitting Issues (Resolved)
-
✅ Slide 5 (Core Architecture): Split into:
- 5a: Overview of client-server architecture
- 5b: Detailed components with two-column layout
-
✅ Slide 7 (Communication Flow): Split into:
- 7a: Overview of the flow and protocol
- 7b: Detailed steps with two-column layout
-
✅ Slide 11 (Best Practices): Split into:
- 11a: Security measures
- 11b: Implementation practices with added content
Visual Appeal
Background and Color
- Appropriate use of background colors/gradients
- Title slide has purple gradient
- USB-C slide has blue gradient
- Security slides have red background
- Best practices slides have dark blue background
- Use cases slide has blue gradient
- Conclusion matches title slide for cohesion
- Consistent color scheme throughout
- Good contrast between text and backgrounds
- Strategic use of highlight colors for emphasis (blue, green, red)
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.
- 7d ago First seen · 100 lines · 0 tokens per session scan A 47921c7ef3dc
presentation-review-checklist is a cursor rule published in the GitHub repository SwonVIP/mcp-server-talk (0 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 905 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
080-creative-phase-metrics
description: WHEN entering a creative phase ENSURE comprehensive exploration and validation globs: ["/.md", "/.mdc"] alwaysApply: true.
livkiet-plugins-playai
Agent Framework plugin for voice synthesis with PlayAI API.
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.
cli-error-handling
CLI command error handling patterns.