community-projects

Rules for setting up and maintaining community-focused open-source projects. They require files such as a README, contribution guide, software license, and code-of-conduct document.

In plain words
What is it for?
Checking README contents, contribution instructions, development and testing guidance, licensing details, and community behaviour rules.
Why use it?
They prevent new projects from missing the information contributors need to install, use, improve, and legally share the software.

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/squirrelogic/cursor-rules/community-projects
Clone the repo
git clone --depth 1 https://github.com/squirrelogic/cursor-rules

Made for: Cursor.

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 713 The whole file, excluding the scripts and references it only reads on demand.
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.00009 $0.00713
Opus 5 $0.00005 $0.00357
Sonnet 5 $0.00002 $0.00143
Haiku 4.5 $0.00001 $0.00071

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

Security

Grade A, and why

community-projects 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.cursor/rules/community-projects.mdc · 133 lines

What it actually says

Community Projects Rule

Standards for initializing and maintaining community-focused open source projects.

actions:

  • type: validate description: "Validate required community files" requirements:

    • name: "README.md" required: true content:
      • "Project title and description"
      • "Installation instructions"
      • "Usage examples"
      • "Contributing guidelines reference"
      • "License reference"
    • name: "CONTRIBUTING.md" required: true content:
      • "How to contribute"
      • "Development setup"
      • "Pull request process"
      • "Code style guidelines"
      • "Testing requirements"
    • name: "LICENSE" required: true content:
      • "Valid open source license text"
      • "Current year"
      • "Copyright holder information"
    • name: "CODE_OF_CONDUCT.md" required: true content:
      • "Expected behavior"
      • "Unacceptable behavior"
      • "Reporting process"
      • "Enforcement guidelines"
      • "Contact information"
  • type: suggest message: | When setting up a community project, ensure:

    1. README.md contains:

      # Project Name
      
      Brief description of the project.
      
      ## Installation
      
      Step-by-step installation instructions.
      
      ## Usage
      
      Basic usage examples.
      
      ## Contributing
      
      Please read [CONTRIBUTING.md](mdc:CONTRIBUTING.md) for details on our code of conduct and the process for submitting pull requests.
      
      ## License
      
      This project is licensed under the [LICENSE_NAME] - see the [LICENSE](mdc:LICENSE) file for details.
      
    2. CONTRIBUTING.md contains:

      # Contributing Guidelines
      
      ## Development Setup
      [Development environment setup instructions]
      
      ## Pull Request Process
      1. Update documentation
      2. Update tests
      3. Follow code style
      4. Get reviews
      
      ## Code Style
      [Code style guidelines]
      
      ## Testing
      [Testing requirements and instructions]
      
    3. LICENSE file:

      • Choose appropriate license (MIT, Apache 2.0, etc.)
      • Include current year
      • Include copyright holder
    4. CODE_OF_CONDUCT.md:

      • Based on Contributor Covenant
      • Include contact information
      • Clear enforcement guidelines

examples:

  • input: |

    Bad: Missing required files

    my-project/ ├── src/ └── README.md

    Good: Complete community project setup

    my-project/ ├── src/ ├── README.md ├── CONTRIBUTING.md ├── LICENSE └── CODE_OF_CONDUCT.md output: "Properly configured community project"

metadata: priority: high version: 1.0 tags: - community - documentation - open-source

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 · 133 lines · 9 tokens per session scan A 06eb30fe70df

Subscribe to this mod's changes

community-projects is a cursor rule published in the GitHub repository squirrelogic/cursor-rules (20 stars, last pushed 1y ago), licensed MIT. It adds 9 tokens to every session and 713 once invoked, about $0.0000 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.