cursorrules

Project-specific coding rules for the plugged.in application. They describe its folder layout, code patterns, MCP integrations, and interface conventions.

In plain words
What is it for?
Use them when adding or changing plugged.in features, database code, MCP server management, or user-interface components.
Why use it?
They give an agent the project’s expected structure and style before it changes code, reducing confusion and inconsistent edits.

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/veriteknik/pluggedin-app/cursorrules
Clone the repo
git clone --depth 1 https://github.com/VeriTeknik/pluggedin-app

Made for: Cursor.

Per session 2,788 This file is loaded in full into every session.
When invoked 2,788 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.02788 $0.02788
Opus 5 $0.01394 $0.01394
Sonnet 5 $0.00558 $0.00558
Haiku 4.5 $0.00279 $0.00279

Measured 2d ago against content hash 88c28a985c1d, 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.

.cursorrules · 418 lines

How it starts

The opening of the file, as written. The whole thing — 418 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Plugged.in Project Intelligence Rules

Project Structure Patterns

  1. The app uses a Next.js App Router structure:

    • app/ - Main application folder
    • app/(sidebar-layout)/ - Routes with the sidebar layout
    • app/actions/ - Server actions for backend operations
    • app/api/ - API routes for external access
    • db/ - Database schema and utilities
    • types/ - TypeScript type definitions
    • components/ - Reusable UI components
    • hooks/ - Custom React hooks
  2. MCP server logic is organized as:

    • db/schema.ts - Database schema definitions
    • app/actions/mcp-servers.ts - Server actions for MCP servers
    • app/actions/custom-mcp-servers.ts - Server actions for custom MCP servers
    • types/mcp-server.ts - Type definitions for MCP servers
    • app/(sidebar-layout)/(container)/mcp-servers/ - UI for MCP server management
  3. MCP playground components:

    • app/actions/mcp-playground.ts - Server actions for MCP playground
    • app/actions/playground-settings.ts - Server actions for playground settings
    • app/(sidebar-layout)/(container)/mcp-playground/page.tsx - UI implementation
    • app/(sidebar-layout)/(container)/mcp-playground/README.md - Documentation

Code Patterns

  1. Server-side operations use Next.js server actions:

    'use server';
    
    export async function serverAction(arg1, arg2) {
      // Database operations or other server-side logic
    }
    
  2. Database operations use Drizzle ORM with PostgreSQL:

    import { db } from '@/db';
    import { someTable } from '@/db/schema';
    
    // Query example
    const result = await db.query.someTable.findFirst({
      where: eq(someTable.id, someId)
    });
    
    // Insert example
    await db.insert(someTable).values({
      field1: value1,
      field2: value2
    });
    
  3. Frontend data fetching uses SWR:

    const { data, error, mutate } = useSWR(
      key,
      () => fetchFunction(args)
    );
    

Read the full file on GitHub · 418 lines

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 · 418 lines · 2,788 tokens per session scan A 88c28a985c1d

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository VeriTeknik/pluggedin-app (99 stars, last pushed 7d ago), licensed MIT. It adds 2,788 tokens to every session, about $0.0139 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.