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/LeadMagic/smartlead-mcp-serverWrote 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/leadmagic/smartlead-mcp-server/api-patterns)<a href="https://agentmods.dev/rules/leadmagic/smartlead-mcp-server/api-patterns"><img src="https://agentmods.dev/badge/rules/leadmagic/smartlead-mcp-server/api-patterns/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/leadmagic/smartlead-mcp-server/api-patterns"><img src="https://agentmods.dev/badge/rules/leadmagic/smartlead-mcp-server/api-patterns.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.03222 |
| Opus 5.5 | $0.00000 | $0.01289 |
| Sonnet 5.5 | $0.00000 | $0.00644 |
| Haiku 4.5 | $0.00000 | $0.00322 |
Grade A, and why
api-patterns 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 1mo 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 — 423 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: SmartLead MCP API Development Patterns description: Development patterns for API clients and MCP tools in the SmartLead server author: LeadMagic Team version: 1.0.0
🏗️ SmartLead API Development Patterns & Best Practices
Developer Guide: Master the patterns and practices used throughout the SmartLead MCP Server. This guide will help you write consistent, maintainable code that follows our established conventions.
🎯 Quick Reference
🔥 Most Important Patterns
- Base Client Extension → All API modules extend
BaseSmartLeadClient - MCP Tool Registration → Use the standard registration pattern
- Zod Schema Validation → All inputs validated with Zod
- Error Handling → Use
SmartLeadErrorfor API errors - Type Safety → Avoid
any, use proper TypeScript types
🏗️ SmartLead API Client Architecture
🛠️ Base Client Pattern
File:
src/client/base.ts
The foundation of all API interactions:
export abstract class BaseSmartLeadClient {
protected config: SmartLeadConfig;
constructor(config: SmartLeadConfig) {
this.config = config;
}
// 🔄 Automatic retry with exponential backoff
protected async withRetry<T>(operation: () => Promise<T>): Promise<T> {
// Handles transient failures automatically
}
// 🌐 HTTP methods with proper typing
protected async get<T>(url: string): Promise<T> { }
protected async post<T>(url: string, data: unknown): Promise<T> { }
protected async put<T>(url: string, data: unknown): Promise<T> { }
protected async delete<T>(url: string): Promise<T> { }
}
Key Features:
- ✅ HTTP request handling with Axios
- ✅ Automatic retry logic with exponential backoff
- ✅ Rate limiting and request queuing
- ✅ Error handling with SmartLeadError class
- ✅ Request/response logging for debugging
🔌 Module Structure Pattern
Example:
src/modules/campaigns/client.ts
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.
- 1mo ago First seen · 423 lines · 0 tokens per session scan A e700f4980bf9
api-patterns is a cursor rule published in the GitHub repository LeadMagic/smartlead-mcp-server (21 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,222 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-30.
Other cursor rules, from other repositories
architecture
Architecture of openapi-to-cli (ocli).
mcp-debugging
The mcp-debug agent provides essential tools to test and explore MCP (Model Context Protocol) servers. This guide focuses on using the agent to debug MCP server behavior and functionality.
handle-rate-limiting-responses
Cursor rule "handle-rate-limiting-responses" from PaulJPhilp/EffectPatterns, covering handle rate limiting responses and example.
control-repetition-with-schedule
Cursor rule "control-repetition-with-schedule" from PaulJPhilp/EffectPatterns, covering control repetition with schedule and example.
cursorrules
You have access to the now-sdk-ext-mcp MCP server for ServiceNow platform operations. Use these rules when interacting with ServiceNow instances.
define-a-type-safe-configuration-schema
Cursor rule "define-a-type-safe-configuration-schema" from PaulJPhilp/EffectPatterns, covering define a type-safe configuration schema and example.