Borrowing it
Nothing to install: this file belongs to enuno/unifi-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/enuno/unifi-mcp-server/main/.claude/commands/unifi-mcp-update-docs.mdgit 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/commands/enuno/unifi-mcp-server/unifi-mcp-update-docs)<a href="https://agentmods.dev/commands/enuno/unifi-mcp-server/unifi-mcp-update-docs"><img src="https://agentmods.dev/badge/commands/enuno/unifi-mcp-server/unifi-mcp-update-docs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/enuno/unifi-mcp-server/unifi-mcp-update-docs"><img src="https://agentmods.dev/badge/commands/enuno/unifi-mcp-server/unifi-mcp-update-docs.svg" alt="Reviewed on agentmods" width="80" 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.00012 | $0.00821 |
| Opus 5 | $0.00006 | $0.00411 |
| Sonnet 5 | $0.00002 | $0.00164 |
| Haiku 4.5 | $0.00001 | $0.00082 |
Grade A, and why
unifi-mcp-update-docs 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 11d 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
Automatically generate and update API.md documentation from tool docstrings and code.
This command scans all MCP tools and resources, extracts documentation from code, and updates API.md to ensure it stays in sync with the implementation.
Steps to execute:
-
Discover all MCP tools:
- Scan
src/tools/directory for all tool modules - Import each module and extract tool functions
- Parse docstrings to get:
- Description
- Parameters with types and descriptions
- Return values
- Raises (errors)
- Example usage
- Scan
-
Discover all MCP resources:
- Scan
src/resources/directory for resource handlers - Extract resource URI templates
- Document available operations (list, read, subscribe)
- Scan
-
Categorize tools by functionality:
- Site Management
- Device Operations
- Client Management
- Network Configuration
- WiFi/WLAN Management
- Firewall & Security
- Port Forwarding
- DPI (Deep Packet Inspection)
- Zone-Based Firewall
- Traffic Flows
- Vouchers
- Webhooks
-
Read current API.md to preserve:
- Overview and introduction sections
- Authentication details
- Rate limiting information
- Error handling guide
- Custom examples or notes
-
Generate updated documentation:
-
Table of contents with all categories
-
Tool documentation for each category:
### tool_name **Description:** Brief description **Parameters:** - `param1` (type): Description - `param2` (type, optional): Description **Returns:** Return value description **Example:** ```json { "tool": "tool_name", "arguments": { "param1": "value1" } }
-
-
Update API.md:
- Preserve manual sections (overview, auth, errors)
- Replace tool documentation sections
- Add new tools that aren't documented
- Remove documentation for deleted tools
- Update version number and last updated date
-
Validate documentation:
- Check for missing descriptions
- Verify all parameters are documented
- Ensure examples are valid JSON
- Check for broken internal links
Report back with:
- Number of tools documented
- Number of resources documented
- Tools added to documentation
- Tools removed from documentation
- Tools with incomplete documentation
- Summary of changes made
- Validation results
Example output:
Documentation Update Complete!
Tools Documented: 40
Resources Documented: 4
Changes:
✓ Added documentation for 2 new tools:
- create_traffic_flow_rule
- update_zbf_matrix
✓ Updated 5 tool descriptions
✓ Removed 1 deprecated tool: old_firewall_rule
⚠ Warning: 3 tools missing example usage:
- get_device_stats
- list_dpi_restrictions
- create_port_forward
Categories:
- Site Management: 3 tools
- Device Operations: 6 tools
- Client Management: 5 tools
- Network Configuration: 4 tools
- WiFi/WLAN: 4 tools
- Firewall & Security: 8 tools
- Zone-Based Firewall: 5 tools
- Traffic Flows: 3 tools
- Other: 2 tools
API.md updated successfully!
Last updated: 2025-01-15
Safety checks:
- Never expose credentials in examples
- Use placeholder values for sensitive data
- Preserve existing manual documentation
- Create backup before major changes
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.
- 11d ago First seen · 146 lines · 12 tokens per session scan A a9e5d038beb1
unifi-mcp-update-docs is a command published in the GitHub repository enuno/unifi-mcp-server (250 stars, last pushed 4d ago), licensed Apache-2.0. It adds 12 tokens to every session and 821 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.