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/enuno/unifi-mcp-server/mcp-toolsgit clone --depth 1 https://github.com/enuno/unifi-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/enuno/unifi-mcp-server/mcp-tools)<a href="https://agentmods.dev/rules/enuno/unifi-mcp-server/mcp-tools"><img src="https://agentmods.dev/badge/rules/enuno/unifi-mcp-server/mcp-tools.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.00600 | $0.00600 |
| Opus 5 | $0.00300 | $0.00300 |
| Sonnet 5 | $0.00120 | $0.00120 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
mcp-tools 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 7d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Tool Implementation Pattern
Every MCP tool should follow this structure:
from typing import Optional, Literal
from pydantic import BaseModel, Field
from fastmcp import FastMCP
mcp = FastMCP("UniFi MCP Server")
@mcp.tool()
async def tool_name(
# Required parameters first
site_id: str,
resource_id: str,
# Optional parameters with defaults
optional_param: Optional[str] = None,
# Safety parameters for mutating operations
confirm: bool = False,
dry_run: bool = False
) -> dict:
"""
Clear, concise description of what the tool does.
Args:
site_id: Always include site_id for multi-site support
resource_id: Specific resource identifier
optional_param: Description of optional parameter
confirm: REQUIRED True for mutating operations (safety)
dry_run: Preview changes without applying them
Returns:
Dictionary with operation results. Specify structure.
Raises:
MCPError: For all MCP-specific errors
ValueError: For invalid inputs
UniFiConnectionError: For API connection issues
"""
# 1. Input validation
if not site_id:
raise ValueError("site_id is required")
# 2. Safety checks for mutating operations
if not confirm and not dry_run:
raise MCPError("This operation requires confirm=True")
# 3. Audit logging
logger.info(
f"tool_name: site={site_id}, id={resource_id}, dry_run={dry_run}",
extra={"operation": "tool_name", "site_id": site_id}
)
# 4. Dry-run mode
if dry_run:
preview = await generate_preview(site_id, resource_id)
return {"status": "preview", "changes": preview}
# 5. Execute operation
try:
result = await execute_operation(site_id, resource_id)
except UniFiAPIError as e:
logger.error(f"Operation failed: {e}")
raise MCPError(f"Failed to execute operation: {str(e)}")
# 6. Cache invalidation (if applicable)
if result.get("success"):
await cache.invalidate(f"resource:{site_id}")
# 7. Return structured result
return {
"status": "success",
"resource_id": resource_id,
"data": result
}
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.
- 7d ago First seen · 94 lines · 600 tokens per session scan A 3bc2d602dbda
mcp-tools is a cursor rule published in the GitHub repository enuno/unifi-mcp-server (245 stars, last pushed 4d ago), licensed Apache-2.0. It adds 600 tokens to every session, about $0.0030 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-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.