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/gargoyle92/agentify-mcp/02-mcp-protocol-standardsgit clone --depth 1 https://github.com/gargoyle92/agentify-mcpWrote 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/gargoyle92/agentify-mcp/02-mcp-protocol-standards)<a href="https://agentmods.dev/rules/gargoyle92/agentify-mcp/02-mcp-protocol-standards"><img src="https://agentmods.dev/badge/rules/gargoyle92/agentify-mcp/02-mcp-protocol-standards.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.00889 | $0.00889 |
| Opus 5 | $0.00445 | $0.00445 |
| Sonnet 5 | $0.00178 | $0.00178 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
02-mcp-protocol-standards 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
02-MCP-Protocol-Standards
MCP Protocol Implementation
This project implements the Model Context Protocol (MCP) using @modelcontextprotocol/sdk.
Core MCP Components
- Server: agentify-mcp.ts implements the main MCP server
- Tools: tool-registry.ts manages MCP tool implementations
- Resources: resource-manager.ts handles MCP resource serving
CRITICAL MCP RULES - MUST FOLLOW
✅ ALWAYS DO:
- Use proper schemas: All tool definitions MUST use proper inputSchema with type, properties, and required fields
- Validate tool arguments: Always validate incoming tool arguments against the schema
- Return proper response format: Tools must return objects that match MCP response expectations
- Handle client detection: Use AgentClientType to provide client-specific tools and resources
- Implement proper URI schemes: Resources must use
agentify://URI scheme consistently
❌ NEVER DO:
- Skip input validation: Never execute tools without validating input parameters
- Return raw strings for complex data: Use structured objects, not plain strings for tool responses
- Hardcode resource URIs: Always use the established
agentify://URI pattern - Ignore client context: Never provide tools/resources without checking client type compatibility
- Break MCP schema compliance: All responses must conform to MCP protocol specifications
Tool Implementation Standards
Required Tool Structure:
{
name: string; // kebab-case naming
description: string; // Clear, actionable description
inputSchema: {
type: 'object';
properties: Record<string, any>; // Detailed parameter definitions
required?: string[]; // List required parameters
};
clientTypes?: AgentClientType[]; // Specify compatible clients
handler: (args: any, client: AgentClient) => Promise<any>;
}
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 · 111 lines · 889 tokens per session scan A 7eb7355f00b1
02-mcp-protocol-standards is a cursor rule published in the GitHub repository gargoyle92/agentify-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 889 tokens to every session, about $0.0044 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-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.