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 instructions/devjourney/unifi-mcp/agents-mdgit clone --depth 1 https://github.com/devjourney/unifi-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/instructions/devjourney/unifi-mcp/agents-md)<a href="https://agentmods.dev/instructions/devjourney/unifi-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/devjourney/unifi-mcp/agents-md.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.04721 | $0.04721 |
| Opus 5 | $0.02361 | $0.02361 |
| Sonnet 5 | $0.00944 | $0.00944 |
| Haiku 4.5 | $0.00472 | $0.00472 |
Grade A, and why
unifi-mcp AGENTS.md 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.
This is a copy
100% identical to unifi-mcp AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Rules
Non-Goals
This project is not:
- a general-purpose network management framework
- a UniFi controller replacement or admin dashboard
- a real-time monitoring or alerting service
- a CI/CD pipeline runner or deployment tool
- a web application with a frontend UI (dev consoles are debugging REPLs only)
- a database or persistent storage layer (all state lives on UniFi controllers)
Architecture Rules
Layering
- Tool functions MUST NOT contain business logic beyond argument validation and response formatting
- Tool functions MUST delegate to manager methods for all controller interactions
- Manager methods MUST NOT import from
<app>.tools(no circular dependencies) - All controller communication MUST flow through
ConnectionManager - Tool modules MUST import singletons from
<app>.runtime, never instantiate directly - Shared packages MUST NOT import from app packages (dependency flows downward only)
- App packages MUST NOT import from each other (no cross-app dependencies)
Singletons
- All shared objects (server, config, managers) MUST be created via
@lru_cachefactories in<app>/runtime.py - Tests MUST monkey-patch the factory or alias before importing tool modules
- There MUST be exactly one
ConnectionManagerinstance per server process
Tool Response Contract
All tools MUST return Dict[str, Any]:
{"success": True, "data": <result>} # Success
{"success": False, "error": "<specific, actionable message>"} # Error
{"success": True, "requires_confirmation": True, "preview": <payload>} # Mutation preview
- Exceptions MUST NOT escape tool functions. Catch, log with
exc_info=True, return error dict. - Error messages MUST include the operation that failed (e.g.,
"Failed to list devices: ..."not juststr(e)). - Raw tracebacks MUST NOT be exposed to MCP clients.
Confirmation System
All state-changing tools MUST implement preview-then-confirm:
confirm=False(default): validate input, return preview payloadconfirm=True: execute the mutation on the controller- Bypass mode injects
confirm=Trueautomatically - Anchor:
packages/unifi-mcp-shared/src/unifi_mcp_shared/confirmation.py
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 · 292 lines · 4,721 tokens per session scan A 9aeae64ec972
unifi-mcp AGENTS.md is an instructions file published in the GitHub repository devjourney/unifi-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 4,721 tokens to every session, about $0.0236 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to unifi-mcp AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.