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/swonvip/mcp-server-talk/presentation-guidelinesgit clone --depth 1 https://github.com/SwonVIP/mcp-server-talkWhat 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.00486 | $0.00486 |
| Opus 5 | $0.00243 | $0.00243 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
presentation-guidelines 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Presentation Structure Guidelines
General Structure
- Keep slides simple and focused on one main point per slide
- Use consistent styling throughout your presentation
- Consider your audience's perspective and needs
- Aim for 1-2 minutes per slide on average
Content Guidelines
- Use short, concise bullet points instead of paragraphs
- Include relevant images, diagrams, or charts to illustrate points
- Keep code examples short and highlight important parts
- Use transitions and animations purposefully, not gratuitously
Technical Tips
- Test your presentation in the environment where you'll present
- Ensure all media (images, videos) is properly loaded
- Have a backup plan in case of technical difficulties
- Practice navigating through your slides, including vertical navigation
reveal.js Features to Consider
- Speaker notes (press 's' during presentation)
- PDF export for handouts
- Overview mode (press 'o' or 'ESC')
- Slide fragments for step-by-step reveals
- Code syntax highlighting
- Markdown support for content
- Auto-animate for smooth transitions between slides
- Mobile touch navigation
Installation Options
- Basic setup: Download ZIP from GitHub and extract
- Full setup (recommended):
git clone https://github.com/hakimel/reveal.js.git cd reveal.js npm install npm start - Install from npm:
npm install reveal.js
Essential Keyboard Shortcuts
- Next slide: Space, Right Arrow, Down Arrow, Page Down, 'n'
- Previous slide: Left Arrow, Page Up, 'p'
- Overview: 'Esc' or 'o'
- Speaker notes: 's'
- Fullscreen: 'f'
- Zoom: Alt + click (or Ctrl + click for Windows)
- Pause presentation: 'b' or '.'
Resources
- Documentation: https://revealjs.com/
- GitHub repository: https://github.com/hakimel/reveal.js/
- Themes gallery: https://revealjs.com/themes/
- Plugins: https://revealjs.com/plugins/
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 · 73 lines · 486 tokens per session scan A dcb63172145d
presentation-guidelines is a cursor rule published in the GitHub repository SwonVIP/mcp-server-talk (0 stars, last pushed 1y ago), licensed MIT. It adds 486 tokens to every session, about $0.0024 per session on Opus 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
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.