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/unifi-apigit 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/unifi-api)<a href="https://agentmods.dev/rules/enuno/unifi-mcp-server/unifi-api"><img src="https://agentmods.dev/badge/rules/enuno/unifi-mcp-server/unifi-api.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.01158 | $0.01158 |
| Opus 5 | $0.00579 | $0.00579 |
| Sonnet 5 | $0.00232 | $0.00232 |
| Haiku 4.5 | $0.00116 | $0.00116 |
Grade A, and why
unifi-api 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 6d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UniFi API Guidelines
Authentication with API Keys
This project uses the official UniFi Cloud API with API key authentication.
Authentication Method:
- Use
UNIFI_API_KEYenvironment variable for authentication - API key is passed via the
X-API-KeyHTTP header - No session management or cookies required (stateless authentication)
NEVER hardcode API keys:
# ❌ BAD - Hardcoded API key
headers = {
"X-API-Key": "abc123def456..."
}
# ✅ GOOD - Load from environment
from src.config.config import Settings
settings = Settings()
headers = {
"X-API-Key": settings.api_key
}
API Access Modes
Support both cloud and local gateway access modes:
Cloud API (Default):
# Base URL: https://api.ui.com/v1/
settings.api_type = "cloud"
settings.cloud_api_url = "https://api.ui.com"
Local Gateway Proxy:
# Base URL: https://{gateway-ip}/proxy/network/integration/v1/
settings.api_type = "local"
settings.local_host = "192.168.2.1"
settings.local_port = 443
Read-Only Limitation
IMPORTANT: The Early Access API is currently read-only.
# ✅ ALLOWED - Read operations
async def list_devices(site_id: str):
"""List all devices - read operation."""
devices = await client.get(f"/v1/sites/{site_id}/devices")
return devices
# ❌ NOT AVAILABLE - Write operations (will fail)
async def create_network(name: str, vlan_id: int):
"""Create network - not yet supported in EA API."""
# This will return 403 Forbidden in current API version
raise NotImplementedError(
"Write operations are not available in the Early Access API. "
"This feature will be available in v1 Stable release."
)
Handling write requests:
- Document that write operations are not yet available
- Return clear error messages to users
- Consider implementing a "preview" mode that shows what would be created
- Monitor UniFi API release notes for v1 Stable availability
Rate Limiting Considerations
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.
- 6d ago First seen · 194 lines · 1,158 tokens per session scan A 705d94512d58
unifi-api 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 1,158 tokens to every session, about $0.0058 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
cursorrules
Robot control server. Do not move the physical robot without checking health first.
20-angular-services
Angular service rules for wrapping web-serial-rxjs.
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.