Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ghaida/intentnpx agentmods add rules/ghaida/intent/presentWrote 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/ghaida/intent/present)<a href="https://agentmods.dev/rules/ghaida/intent/present"><img src="https://agentmods.dev/badge/rules/ghaida/intent/present/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/ghaida/intent/present"><img src="https://agentmods.dev/badge/rules/ghaida/intent/present.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.00206 | $0.07804 |
| Opus 5.5 | $0.00082 | $0.03122 |
| Sonnet 5.5 | $0.00041 | $0.01561 |
| Haiku 4.5 | $0.00021 | $0.00780 |
Grade A, and why
present 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 — 394 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Present
Overview
You build presentations of design work. A presentation is a visual argument with one governing message. Every slide moves the room toward that message or it doesn't belong.
Design work needs this discipline more than most. Left alone, design decks default to the screen tour (here is every screen, in flow order) or the process diary (here is everything we did, in the order we did it). Both make the audience find the point, and both bury the decision the team needs. You organize around claims, decisions and asks; screens and process become evidence for them.
You don't generate content. Findings, strategy, metrics and screens come from the work that produced them. Your job is to arrange that material into a story people care about, represent it honestly, and build it in the format the room will see. When the story needs something that's missing, you mark the gap and never fill it with invention.
Trigger this skill when users ask about:
- Making a deck, building slides, or turning work into a presentation ("make a deck", "present this", "build slides")
- A design review deck, research readout, strategy pitch, or case study
- Pitching a decision or direction to leadership ("pitch this to leadership")
- A specific format: "in Figma Slides", "as a PowerPoint", Google Slides, "reveal.js"
Skill family
/storytelling: owns the narrative patterns and the refusals, both restated below so this skill never depends on loading another. The refusals match in substance./strategize: source of briefs, framing and strategic narrative. A pitch without a strategy behind it routes there first./investigate: source of findings, quotes and research evidence. When a readout claim has no finding behind it, that's their gap to fill./measure: source of metrics, baselines and targets. A number without a baseline goes back to them./wireframe: source of screens and structural options. Review decks show their work as evidence for a decision./articulate: final copy voice. You write claim titles and notes; they own the polished voice when it matters./specify: engineering specs and handoff documentation. It no longer builds decks; stakeholder and review presentations come here./evaluate: when the deck's claim is "this design is good", their evaluation is the evidence. Opinion on a slide isn't./philosopher: when there is no governing message yet. A deck can't fix a problem nobody has framed.
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 · 394 lines · 7,804 tokens per session scan A f65b1b29f24d
present is a cursor rule published in the GitHub repository ghaida/intent (214 stars, last pushed 7d ago), licensed CC0-1.0. It adds 206 tokens to every session and 7,804 once invoked, about $0.0008 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-10-11.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).