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/context7-integrationgit 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/context7-integration)<a href="https://agentmods.dev/rules/openstory-so/openstory/context7-integration"><img src="https://agentmods.dev/badge/rules/openstory-so/openstory/context7-integration.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.00691 | $0.00691 |
| Opus 5 | $0.00345 | $0.00345 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
context7-integration 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context7 MCP Integration
Always use Context7 MCP when you need current documentation for:
- Code generation and setup steps
- Library/API documentation
- Configuration examples
- Framework-specific patterns
This means you should automatically use the Context7 MCP tools to resolve library IDs and get library docs without me having to explicitly ask.
Pre-configured Library IDs
Use these Context7 library IDs for OpenStory's tech stack:
Core Framework
/vercel/next.js- Next.js 15 documentation and patterns/microsoft/typescript- TypeScript best practices/facebook/react- React 19 features and hooks
UI & Styling
/tailwindlabs/tailwindcss- Tailwind CSS 4 utilities and configuration/radix-ui/primitives- Radix UI component APIs/shadcn/ui- shadcn/ui component library
Backend & Data
/elysiajs/elysia- Elysia web framework patterns/drizzle-team/drizzle-orm- Drizzle ORM queries and migrations/temporalio/sdk-typescript- Temporal TypeScript SDK/tanstack/query- TanStack Query v5 patterns/arktypeio/arktype- ArkType runtime validation (backend validation)
AI Integration
/fal-ai/client- Fal.ai SDK for image/video generation/openai/openai-node- OpenAI API for script analysis
Infrastructure
/upstash/redis- Redis for caching (via @upstash/redis)/oven-sh/bun- Bun runtime and package manager
When to Use Context7
Automatically invoke Context7 when:
- Setting up new components or features
- Working with framework-specific APIs (Next.js 15 App Router, React Server Components)
- Implementing authentication patterns (Better Auth)
- Configuring AI model integrations (Fal.ai models)
- Working with async job queues (QStash patterns)
- Implementing real-time features (Supabase Realtime)
- Setting up validation schemas (Zod)
- Troubleshooting integration issues
- Learning new library features
OpenStory-Specific Context Needs
Prioritize Context7 for:
- Next.js 15: Server Actions, async request params, React 19 features
- Elysia: Route handlers, plugins, lifecycle hooks
- Drizzle ORM: Query patterns, relations, migrations
- Temporal: Workflow definitions, activity patterns, worker setup
- TanStack Query: Query keys factory pattern, optimistic updates
- Fal.ai: Model-specific parameters (flux, imagen4, veo3, kling, wan)
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 · 79 lines · 691 tokens per session scan A bd81025fc716
context7-integration is a cursor rule published in the GitHub repository openstory-so/openstory (568 stars, last pushed yesterday), licensed MIT. It adds 691 tokens to every session, about $0.0035 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.