cursorrules

A set of Cursor rules for the Pandoras-Shell project, generated by the dotai command-line tool. The rules tell an assistant where to find project context and which conventions, security requirements, and performance targets to follow.

In plain words
What is it for?
Use them when assisting with Pandoras-Shell so the agent checks the .ai directory, follows project conventions, respects locked folders, and references file IDs in documentation and comments.
Why use it?
They keep coding assistance aligned with the project's documented structure, dependency-injection pattern, session management, audit logging, and file-locking rules.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/andrewhopper/itmcp/cursorrules
Clone the repo
git clone --depth 1 https://github.com/andrewhopper/itmcp

Made for: Cursor.

Per session 160 This file is loaded in full into every session.
When invoked 160 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00160 $0.00160
Opus 5 $0.00080 $0.00080
Sonnet 5 $0.00032 $0.00032
Haiku 4.5 $0.00016 $0.00016

Measured 2d ago against content hash 2b305e2310c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cursorrules 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 2d 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.

.ai/0-ai-config/.cursorrules · 32 lines

What it actually says

// Cursor AI rules for Pandoras-Shell // Generated by dotai CLI

// Project context You are assisting with Pandoras-Shell, which follows the Dot AI structure. Review the content in the .ai directory to understand project context.

// Architecture This project uses the following architectural patterns:

// Design Patterns Key design patterns:

  • Dependency Injection

// Security Level: Enterprise Security features required:

  • Session Management
  • Audit Logging

// Performance Targets

  • Scalability: High (10000+ users)
  • Response Time: 200ms

// Development Environments

local host only

// Guidelines

  • Reference file IDs in documentation and code comments
  • Check folder-locks.md before modifying locked directories
  • Follow project conventions from .ai/1-context/project_conventions.md
Changes

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.

  1. 2d ago First seen · 32 lines · 160 tokens per session scan A 2b305e2310c2

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository andrewhopper/itmcp (16 stars, last pushed 1y ago), licensed MIT. It adds 160 tokens to every session, about $0.0008 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.