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/diegomarino/awesomic-cursor-rules/contributing-mdgit clone --depth 1 https://github.com/diegomarino/awesomic-cursor-rulesWrote 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/diegomarino/awesomic-cursor-rules/contributing-md)<a href="https://agentmods.dev/rules/diegomarino/awesomic-cursor-rules/contributing-md"><img src="https://agentmods.dev/badge/rules/diegomarino/awesomic-cursor-rules/contributing-md.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.00000 | $0.01254 |
| Opus 5 | $0.00000 | $0.00627 |
| Sonnet 5 | $0.00000 | $0.00251 |
| Haiku 4.5 | $0.00000 | $0.00125 |
Grade A, and why
contributing-md 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.
How it starts
The opening of the file, as written. The whole thing — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contributing Standards
Basic Structure
required_sections:
- Welcome Message
- Code of Conduct Reference
- Getting Started Guide
- Development Workflow
- Pull Request Process
- Technical Documentation
- Testing Guidelines
- Style Guidelines
- Contact Information
optional_sections:
- Project Architecture
- Development Environment
- Common Issues
- Performance Guidelines
- Security Guidelines
- Release Process
- Community Guidelines
Section Guidelines
Welcome Section
# Contributing to [Project Name]
First off, thank you for considering contributing to [Project Name]. It's people like you that make [Project Name] such a great tool.
This document provides guidelines and steps for contributing.
Getting Started
steps:
- Fork the repository
- Clone your fork
- Set up development environment
- Create feature branch
- Make changes
- Run tests
- Submit pull request
environment_setup:
- Required tools
- Configuration steps
- Verification commands
Development Workflow
branching_strategy:
main: Production-ready code
develop: Integration branch
feature: Feature development
bugfix: Bug fixes
release: Release preparation
naming_conventions:
features: feature/<issue-number>-brief-description
bugfix: fix/<issue-number>-brief-description
release: release/v<major>.<minor>.<patch>
Technical Documentation
Architecture Overview
graph TD
A[Core Module] --> B[Service Layer]
B --> C[Data Access]
B --> D[External APIs]
E[Utils] --> A
E --> B
Component Documentation
format:
name: ComponentName
purpose: Brief description
dependencies: [List of dependencies]
api_endpoints: [List of endpoints]
events: [List of events]
configuration: [Configuration options]
Detailed Workflows
documentation:
- Component interactions
- Data flow diagrams
- State management
- Error handling
- Performance considerations
- Security measures
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 · 292 lines · 0 tokens per session scan A eb05b0d0008a
contributing-md is a cursor rule published in the GitHub repository diegomarino/awesomic-cursor-rules (10 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,254 tokens. 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.
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.