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/squirrelogic/mcp-feature-discussion/community-projectsgit clone --depth 1 https://github.com/squirrelogic/mcp-feature-discussionWrote 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/squirrelogic/mcp-feature-discussion/community-projects)<a href="https://agentmods.dev/rules/squirrelogic/mcp-feature-discussion/community-projects"><img src="https://agentmods.dev/badge/rules/squirrelogic/mcp-feature-discussion/community-projects.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.00009 | $0.00713 |
| Opus 5 | $0.00005 | $0.00357 |
| Sonnet 5 | $0.00002 | $0.00143 |
| Haiku 4.5 | $0.00001 | $0.00071 |
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 4d 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.
This is a copy
100% identical to community-projects — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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"
- name: "README.md"
required: true
content:
-
type: suggest message: | When setting up a community project, ensure:
-
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. -
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] -
LICENSE file:
- Choose appropriate license (MIT, Apache 2.0, etc.)
- Include current year
- Include copyright holder
-
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
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.
- 4d ago First seen · 133 lines · 9 tokens per session scan A 06eb30fe70df
community-projects is a cursor rule published in the GitHub repository squirrelogic/mcp-feature-discussion (1 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. It is 100% identical to community-projects, differing in 0 lines, and is treated as a copy.
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.
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.
family-instance-domain-actions
Family instance domain action implementation patterns.