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 skills/pproenca/unifi-mcp/docs-syncnpx skills add pproenca/unifi-mcp --skill docs-syncgit clone --depth 1 https://github.com/pproenca/unifi-mcpWhat 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.00042 | $0.00450 |
| Opus 5 | $0.00021 | $0.00225 |
| Sonnet 5 | $0.00008 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
docs-sync 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.
What it actually says
Docs Sync
Overview
Identify doc coverage gaps and inaccuracies by comparing the current implementation (MCP tools, types, API endpoints) against the docs structure, then propose targeted improvements.
Workflow
-
Confirm scope and base branch
- Identify the current branch and default branch (usually
main). - If not on
main, analyze only the diff vsmainto scope doc updates.
- Identify the current branch and default branch (usually
-
Build a feature inventory
- Inventory the MCP tools surface: all tools in
src/, their parameters, and descriptions. - Cross-reference with the scraped UniFi API docs in
docs/api/. - Check that tool descriptions match the OpenAPI spec at
docs/api/openapi.json. - Note any endpoints in the spec that don't have corresponding MCP tools.
- Inventory the MCP tools surface: all tools in
-
Doc-first pass: review existing pages
- Walk each relevant page under
docs/. - Identify missing mentions of tools, configuration options, or setup instructions.
- Walk each relevant page under
-
Code-first pass: map features to docs
- Review
src/exports and tool definitions. - Determine the best doc page for each feature.
- Identify features that lack any documentation.
- Review
-
Detect gaps and inaccuracies
- Missing: tools/features present in code but absent in docs.
- Incorrect/outdated: descriptions that diverge from the current implementation.
- Structural issues: pages overloaded or mis-grouped.
-
Produce a Docs Sync Report and ask for approval before editing.
Output format
Docs Sync Report
- Doc-first findings
- Page + missing content → evidence + suggested insertion point
- Code-first gaps
- Feature + evidence → suggested doc page/section
- Incorrect or outdated docs
- Doc file + issue + correct info + evidence
- Proposed edits
- Doc file → concise change summary
- Questions for the user
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 · 55 lines · 42 tokens per session scan A 19ef046a14bc
docs-sync is a skill published in the GitHub repository pproenca/unifi-mcp (2 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 450 once invoked, about $0.0002 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 skills, from other repositories
unifi-cli
Use when asked about UniFi network gear or the local network — access points, gateway, switches, WiFi, or which clients/devices are connected. Queries the local UniFi gateway via the unifi CLI.
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-linter
MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…