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/chinkan/ai-marp-templateWrote 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/chinkan/ai-marp-template/marp-slides)<a href="https://agentmods.dev/rules/chinkan/ai-marp-template/marp-slides"><img src="https://agentmods.dev/badge/rules/chinkan/ai-marp-template/marp-slides.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.02391 |
| Opus 5 | $0.00000 | $0.01196 |
| Sonnet 5 | $0.00000 | $0.00478 |
| Haiku 4.5 | $0.00000 | $0.00239 |
Grade A, and why
marp-slides 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marp Presentation Rules
Context
This project uses Marp (Markdown Presentation Ecosystem) to generate slides from Markdown.
- Slides Directory:
src/slides/(user-created presentations) - Demo Directory:
src/demo/(theme showcases and examples) - Themes:
src/themes/(custom CSS themes) - Assets:
src/assets/(images, icons, videos) - Engine:
@marp-team/marp-cli
1. Pre-Generation Research Requirement (CRITICAL)
Before generating or modifying slides, you MUST:
- Search for latest Marp syntax (Context7): Always use
mcp_context7_query-docsto consult official documentation for the most up-to-date Marp syntax, directives, and features. - Search for Best Practices (Web): Use
web_searchto research current presentation design trends and best practices (e.g., "effective slide layouts 2024"). - Verify syntax: Ensure any directives (e.g.,
<!-- _class: invert -->) or image attributes (e.g.,![bg right:40%]) are currently supported.
2. Trigger Commands
@slide - Create NEW Presentation
When user inputs @slide followed by ideas/points, ALWAYS create a NEW slide file:
- Parse & Plan:
- Extract the core topic and key points.
- Generate a filename from the topic (kebab-case, e.g.,
project-alpha-launch.md) - Theme Selection: Suggest or select a theme based on content tone:
- Business/Formal ->
corporate - Code/Tech ->
developer - Creative/Marketing ->
gradient - Clean/Academic ->
minimal - Elegant/Evening ->
midnight
- Business/Formal ->
- Structure the presentation:
- Title Slide: Title, Subtitle, Presenter Name.
- Agenda/Overview: Brief list of what will be covered.
- Content Slides: Break down points (1 idea per slide).
- Conclusion: Summary and Q&A.
- Generate Content:
- Create new file in
src/slides/<topic-name>.md - Apply Presentation Best Practices (see below).
- Use appropriate Marp syntax for layout and styling.
- Create new file in
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 · 227 lines · 0 tokens per session scan A b15be474831b
marp-slides is a cursor rule published in the GitHub repository chinkan/ai-marp-template (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,391 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
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.
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.