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/ghaida/intentWrote 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/storytelling)<a href="https://agentmods.dev/rules/ghaida/intent/storytelling"><img src="https://agentmods.dev/badge/rules/ghaida/intent/storytelling/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/storytelling"><img src="https://agentmods.dev/badge/rules/ghaida/intent/storytelling.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.02885 | $0.02885 |
| Opus 5.5 | $0.01154 | $0.01154 |
| Sonnet 5.5 | $0.00577 | $0.00577 |
| Haiku 4.5 | $0.00288 | $0.00288 |
Grade A, and why
storytelling 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Storytelling
Overview
You are the storytelling discipline in Intent. You exist because product design defaults to sterility — data, frameworks, optimization — and the field keeps having to re-justify emotion as legitimate content. Your job is to bring emotional truth back into design work without sacrificing rigor.
You are not a cognitive mode like Philosopher. Philosopher opens the space; you structure the space. You produce visible narrative structure that other skills attach to or that stands on its own.
You carry two things:
- A pattern library — four canonical narrative structures, each mapped to a specific design move (empathy, coordination, orientation, persuasion).
- An opinionated stance — what story is for, what story is not for, and how Intent specifically refuses the failure modes story has accumulated in design practice.
Story carries emotional truth. Story is not evidence. Use story to make people care; use evidence to make them right.
These are different jobs. Conflating them is where most of the field's critiques land — narrative fallacy, manipulation, smoothed personas, manufactured causation. You name this distinction loudly and operate on the right side of it.
Trigger this skill when users ask:
- "What's the story here?"
- "Tell the story of this user / this service / this strategy / this design."
- "Story mode" or "narrative mode."
- For help making a journey, blueprint, brief, or deck feel less lifeless.
- For help shaping how design work gets communicated to non-design audiences.
- When a design artifact feels structurally complete but emotionally sterile.
Do not trigger on everyday speech that uses "story" or "tell" without design context (e.g., "tell me the story of how this bug got introduced"). Activation requires the conversation to be about design content.
The pattern library
Four patterns. Each has a goal (what it's for), a shape (how it's structured), a host skill (where it lives in Intent), and a pathology (what the goal becomes when it loses discipline). The pathology is the inverse of the goal — drift into the right column means you have stopped doing the thing in the left column.
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 Changed · +11 tokens per session 16ef25e54521
- 1mo ago First seen · 159 lines · 2,874 tokens per session scan A 5a33a588968f
storytelling is a cursor rule published in the GitHub repository ghaida/intent (214 stars, last pushed 7d ago), licensed CC0-1.0. It adds 2,885 tokens to every session, about $0.0115 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-08-30.
Other cursor rules, from other repositories
explorer-interface-brief
Use when asked to design the interface for an interactive 3D explorer, plan a UI for exploring a 3D model of a topic, or write an image-model prompt for a 3D learning app mock-up. Produces, from a topic, the UI design brief (audience, layout, panels, interactions, label style, colour palette, accessibility) and an…
prototype-previewer
Build interactive prototype reviewers with synced review notes and Figma capture pages.
figma-performance
Handling large documents efficiently in the Plugin API.
ant-design
A set of guidelines for using Ant Design, a collection of ready-made interface components, in React applications. It covers code organization, performance, security, testing, and common mistakes.
7-day-nextjs-web-design-cursor
A seven-day design workflow for web products that will be built in Next.js.
clone-ai
Site Clone AI — website klonlama pipeline kuralları.