awesome-cursor-rules-mdc is a generator that creates Cursor MDC rule files from structured library information, using semantic search and language models to gather and organize guidance. Developers use it to produce reusable rules for libraries in Cursor, and the catalogue includes 200 of those rules.
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.
git clone --depth 1 https://github.com/sanjeed5/awesome-cursor-rules-mdcWrote 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/sanjeed5/awesome-cursor-rules-mdc/insomnia)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/insomnia"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/insomnia.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.1 | $0.01838 | $0.01838 |
| Opus 5 | $0.00919 | $0.00919 |
| Sonnet 5 | $0.00368 | $0.00368 |
| Haiku 4.5 | $0.00184 | $0.00184 |
Grade A, and why
insomnia 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 3d 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Insomnia Best Practices (2025)
Insomnia is your primary tool for API interaction, debugging, and automated testing. This guide outlines the definitive best practices for leveraging Insomnia in our API-first development pipeline, emphasizing source control, AI assistance, and CI/CD integration.
1. Code Organization and Structure
Treat your Insomnia collections as source-controlled API contracts. They must be versioned alongside your OpenAPI specifications and application code.
✅ GOOD: Source-Controlled Collections with Environment Variables
Export your workspace or specific collections to JSON/YAML and commit them to Git. Use environment variables for all dynamic values, especially secrets.
// my-api-collection.json (example structure)
{
"_type": "export",
"__export_format": 4,
"__export_date": "2025-01-01T00:00:00.000Z",
"__export_source": "insomnia.desktop.app:v12.0.0",
"resources": [
{
"_id": "env_dev",
"parentId": "wrk_123",
"name": "Development",
"data": {
"base_url": "https://dev.api.example.com",
"api_key": "env_API_KEY", // Reference an OS environment variable
"bearer_token": "" // Populated by pre-request script
},
"color": "#63b3ed",
"_type": "environment"
},
{
"_id": "req_1",
"parentId": "fld_abc",
"name": "Get User Profile",
"url": "{{ base_url }}/users/me",
"method": "GET",
"headers": [
{ "name": "Authorization", "value": "Bearer {{ bearer_token }}" }
],
"authentication": {
"type": "bearer",
"token": "{{ bearer_token }}"
},
"_type": "request"
}
]
}
# .gitignore
*.env.json # Ignore local environment overrides
❌ BAD: Hardcoding URLs or Secrets
Never hardcode https://api.example.com or Authorization: Bearer my-secret-token directly into requests. This breaks reproducibility and compromises security.
2. Common Patterns and Anti-patterns
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.
- 3d ago First seen · 231 lines · 1,838 tokens per session scan A ef11c4eaa36e
insomnia is a cursor rule published in the GitHub repository sanjeed5/awesome-cursor-rules-mdc (3,571 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 1,838 tokens to every session, about $0.0092 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-09-03.
Other cursor rules, from other repositories
python_tests
We use the unit tests to cover internal behavior that can work without the web / backend counterpart. We aim for 95%+ unit test coverage of our Python code in lib/streamlit.
validate-contracts
Assert data shape consistency across system boundaries — live API responses against JSON Schema, key-set comparison across layers, data shape validation for migrations and exports. Catches silent data corruption before deploy.
manual-review.backend
A set of rules for verifying backend-only changes and changes that use different verification channels. It separates evidence the agent can collect from checks that require a person, a production authorization, or a business decision.
create-a-testable-http-client-service
Cursor rule "create-a-testable-http-client-service" from PaulJPhilp/EffectPatterns, covering create a testable http client service, example, 1. define the service, 2. create the live implementation and 3. create the test implementation.
architecture
This document outlines the fundamental architectural principles and patterns for the mcp-debug codebase. Adherence to these guidelines is mandatory to maintain a clean, decoupled, and testable system.
issues-tests
Backend test conventions — QuarkusTest, REST Assured, Given, ArchUnit.