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/openstory-so/openstory/project-contextgit clone --depth 1 https://github.com/openstory-so/openstoryWrote 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/openstory-so/openstory/project-context)<a href="https://agentmods.dev/rules/openstory-so/openstory/project-context"><img src="https://agentmods.dev/badge/rules/openstory-so/openstory/project-context.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 | $0.03055 | $0.03055 |
| Opus 5 | $0.01528 | $0.01528 |
| Sonnet 5 | $0.00611 | $0.00611 |
| Haiku 4.5 | $0.00305 | $0.00305 |
Grade A, and why
project-context 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 5d 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 — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenStory Project Context
You are working on OpenStory, an AI-powered cinematic content creation platform that transforms scripts into consistent, styled video productions.
Project Overview
OpenStory democratizes cinematic content creation through:
- Script-to-storyboard AI: Automatic scene breakdown and frame generation
- Style Stacks: JSON-based presets that ensure consistent artistic vision across AI models
- Multi-model support: Integration with 19+ AI models (Fal.ai, Runway, Kling, etc.)
- Character consistency: LoRA model integration for consistent characters
- Motion generation: Image-to-video with VFX capabilities
Project Architecture
Separated frontend/backend monorepo architecture:
openstory/
├── apps/
│ ├── backend/ # Elysia API server
│ │ ├── src/
│ │ │ ├── index.ts # Elysia app entry point
│ │ │ ├── routes/ # Elysia route handlers
│ │ │ │ ├── sequences.ts
│ │ │ │ ├── frames.ts
│ │ │ │ ├── styles.ts
│ │ │ │ └── jobs.ts
│ │ │ ├── services/ # Business logic layer
│ │ │ │ ├── frame-generator.ts
│ │ │ │ ├── script-analyzer.ts
│ │ │ │ └── style-stack.ts
│ │ │ ├── db/ # Drizzle ORM setup & queries
│ │ │ │ ├── index.ts # Database client
│ │ │ │ ├── schema/ # Drizzle schema definitions
│ │ │ │ └── queries/ # Reusable query functions
│ │ │ ├── workflows/ # Temporal workflows
│ │ │ │ ├── client.ts # Temporal client
│ │ │ │ ├── frame-generation.ts
│ │ │ │ ├── motion-generation.ts
│ │ │ │ └── activities/
│ │ │ ├── plugins/ # Elysia plugins
│ │ │ │ ├── auth.ts # BetterAuth integration
│ │ │ │ ├── cors.ts
│ │ │ │ └── logger.ts
│ │ │ ├── lib/ # Backend utilities
│ │ │ │ ├── ai/ # AI client wrappers
│ │ │ │ ├── storage/ # S3-compatible storage
│ │ │ │ └── errors.ts
│ │ │ └── migrations/ # Drizzle migrations
│ │ └── package.json
│ └── frontend/ # Next.js App Router (UI only)
│ ├── src/
│ │ ├── app/ # Next.js pages & layouts
│ │ │ ├── sequences/ # Sequence pages
│ │ │ ├── (auth)/ # Auth pages
│ │ │ └── layout.tsx
│ │ ├── components/
│ │ │ ├── sequence/ # Storyboard, frame editor
│ │ │ ├── ui/ # shadcn/ui components
│ │ │ └── layout/ # App layout
│ │ ├── hooks/ # TanStack Query hooks (API calls)
│ │ │ ├── use-frames.ts
│ │ │ ├── use-sequences.ts
│ │ │ └── use-user.ts
│ │ └── lib/ # Client-side utilities
│ │ ├── api-client.ts
│ │ └── auth-client.ts
│ └── package.json
├── packages/ # Shared code
│ ├── database/ # Shared DB schema (future)
│ ├── types/ # Shared TypeScript types
│ └── validation/ # Shared Zod schemas
└── docs/ # Architecture & PRD docs
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.
- 5d ago First seen · 337 lines · 3,055 tokens per session scan A 81e31b7b3e0c
project-context is a cursor rule published in the GitHub repository openstory-so/openstory (568 stars, last pushed yesterday), licensed MIT. It adds 3,055 tokens to every session, about $0.0153 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-30.
Other cursor rules, from other repositories
cursorrules
Fleet intro-video pipeline: turns a YAML script into an MP4 by driving Playwright (records the target webapp) or a desktop capture (native apps), speech-mcp (TTS narration), and FFmpeg (compose). 7 MCP tools.
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.