agentmods.dev

general

A set of project-wide coding and workflow rules for an MCP server. It requires the uv tool for Python packages and commands and includes rules for issue work, documentation, and code output.

In plain words
What is it for?
For guiding dependency installation, environment setup, Python execution, GitHub issue work, documentation creation, and the style of generated code and logs.
Why use it?
It keeps package management and common development tasks consistent across the project. It also defines restrictions such as not creating README files unless requested.

Cursor rule for Cursor

4 9mo ago A scan 365 tokens original MIT
View the source file plusplusoneplusplus/mcp
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/plusplusoneplusplus/mcp/general
Clone the repo
git clone --depth 1 https://github.com/plusplusoneplusplus/mcp

Made for: Cursor.

Per session 365 This file is loaded in full into every session.
When invoked 365 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.00365 $0.00365
Opus 5 $0.00182 $0.00182
Sonnet 5 $0.00073 $0.00073
Haiku 4.5 $0.00036 $0.00036

Measured yesterday against content hash 5b0f4ee981f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

general 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 yesterday.

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.

.cursor/rules/general.mdc · 30 lines

What it actually says

  1. Always use uv instead of python/pip for all package management and Python execution:
    • Use uv run instead of python
    • Use uv add instead of pip install
    • Use uv remove instead of pip uninstall
    • Use uv sync instead of pip install -r requirements.txt
    • Use uv lock to update dependencies
    • Use existing virtual environment if available, otherwise use uv venv for virtual environment creation
  2. Do not generate readme markdown files unless I explicitly ask
  3. Do not generate example unless I explicitly ask
  4. No Emojis in Code: Never use emojis in code, logging statements, comments, or any programmatic output. Keep all code and logging professional and text-based only
  5. GitHub Issue Resolution Workflow: When the user asks to resolve, work on, or implement a GitHub issue, follow the comprehensive workflow defined in @github_issue_workflow.mdc. This includes:
    • Pre-work setup (checkout main, pull latest changes)
    • Issue analysis and planning
    • Implementation with proper branch management
    • Quality assurance and testing
    • Mandatory pre-submission code review
    • Pull request creation and management
    • Post-submission monitoring and cleanup
  6. GitHub Issue Creation Workflow: When the user asks to create a GitHub issue, follow the structured approach defined in @generate_github_issue.mdc. This includes:
    • Repository identification and verification
    • Issue analysis and requirement clarification
    • Proper issue structure with categorized titles
    • Comprehensive descriptions with acceptance criteria
    • Appropriate labels and metadata suggestions
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. yesterday First seen · 30 lines · 365 tokens per session scan A 5b0f4ee981f2

Subscribe to this mod's changes

general is a cursor rule published in the GitHub repository plusplusoneplusplus/mcp (4 stars, last pushed 9mo ago), licensed MIT. It adds 365 tokens to every session, about $0.0018 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-31.

LanguagesProductivityWriting and docs
Related

Other cursor rules, from other repositories

angular-20

This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.

angular/angular · 0 tokens

dev-standard

Apache Superset development standards and guidelines for Cursor IDE.

apache/superset · 1,147 tokens

typescript

Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.

streamlit/streamlit · 4,669 tokens

coolify-ai-docs

Master reference to all Coolify AI documentation in .ai/ directory.

coollabsio/coolify · 1,426 tokens

python_lib

Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.

streamlit/streamlit · 0 tokens

specs

This directory contains product and tech specs for Streamlit features.

streamlit/streamlit · 0 tokens