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/guzzle)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/guzzle"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/guzzle.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.02910 | $0.02910 |
| Opus 5 | $0.01455 | $0.01455 |
| Sonnet 5 | $0.00582 | $0.00582 |
| Haiku 4.5 | $0.00291 | $0.00291 |
Grade A, and why
guzzle 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 — 422 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guzzle Best Practices
Guzzle is the de-facto PHP HTTP client. Use these rules to build robust, testable, and maintainable HTTP integrations.
1. Client Instantiation & Configuration
Always inject an immutable Guzzle client as a service. Configure it once with global defaults, especially timeouts.
✅ GOOD: Service-Oriented Client with Essential Defaults
<?php
use GuzzleHttp\Client;
use GuzzleHttp\HandlerStack;
use GuzzleHttp\Middleware;
use Psr\Log\LoggerInterface;
use Psr\Http\Message\RequestInterface;
use Psr\Http\Message\ResponseInterface;
use GuzzleHttp\Exception\ConnectException;
use Exception;
final class MyApiClientFactory
{
public static function create(LoggerInterface $logger): Client
{
$stack = HandlerStack::create();
// 1. Logging: Log all requests and responses
$stack->push(Middleware::log(
$logger,
new \GuzzleHttp\MessageFormatter(
'{method} {uri} HTTP/{version} {code} {res_header_Content-Length}'
)
));
// 2. Retry Logic: Robust handling for transient errors (5xx, connection issues)
$stack->push(Middleware::retry(
function (
$retries,
RequestInterface $request,
ResponseInterface $response = null,
Exception $exception = null
) {
// Limit to 3 retries
if ($retries >= 3) {
return false;
}
// Retry on connection exceptions
if ($exception instanceof ConnectException) {
return true;
}
// Retry on server errors (5xx)
if ($response && $response->getStatusCode() >= 500) {
return true;
}
return false;
},
// Exponential backoff: 100ms, 200ms, 400ms
function ($retries) {
return 100 * (2 ** ($retries - 1));
}
));
return new Client([
'base_uri' => 'https://api.example.com/v1/',
'timeout' => 10.0, // Total request timeout in seconds
'connect_timeout' => 5.0, // Connection timeout in seconds
'headers' => [
'Accept' => 'application/json',
'User-Agent' => 'MyApp/1.0 (PHP Guzzle)',
],
'handler' => $stack,
'http_errors' => true, // Throw exceptions for 4xx/5xx responses
]);
}
}
// Usage in a service container or dependency injection
// $client = MyApiClientFactory::create($myLogger);
// $response = $client->get('users');
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 · 422 lines · 2,910 tokens per session scan A b0a421153724
guzzle 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 2,910 tokens to every session, about $0.0145 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
laravel-php-83-cursorrules-prompt-file
Cursor rules for Laravel development with PHP 8.3 integration.
laravel-package-coding-standards
A set of coding rules for Laravel packages, with conventions for names and code across several development areas.
laravel
Core Laravel architecture and coding conventions.
skill-laravel-api
Padrões Globais para Projetos Laravel API (Context Engineering).
laravel-php-auto
Laravel and PHP Development Standards.
php-client-implementation
Guidelines for implementing MCP clients in PHP.