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/secure-ssid/hpe-networking-mcp/network-docsnpx skills add secure-ssid/hpe-networking-mcp --skill network-docsgit clone --depth 1 https://github.com/secure-ssid/hpe-networking-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/skills/secure-ssid/hpe-networking-mcp/network-docs)<a href="https://agentmods.dev/skills/secure-ssid/hpe-networking-mcp/network-docs"><img src="https://agentmods.dev/badge/skills/secure-ssid/hpe-networking-mcp/network-docs.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.00133 | $0.03222 |
| Opus 5 | $0.00067 | $0.01611 |
| Sonnet 5 | $0.00027 | $0.00644 |
| Haiku 4.5 | $0.00013 | $0.00322 |
Grade A, and why
network-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 5d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
network-docs skill
You have access to a local RAG index via the hpe-networking-mcp MCP server.
Always use MCP tools to answer — never guess from model memory alone.
Tool selection
Use the router pattern: find_tool first, then invoke_read_tool.
| Question type | Tool to use | When |
|---|---|---|
| How-to, config, concepts, design | ask_docs |
"how do I configure X", "what is Y", "design guidance for Z" |
| Exact API endpoint / field / enum | lookup_api |
"what endpoint creates X", "what values does field Y accept" |
| Broader keyword search, want raw chunks | search_docs |
exploratory, multiple results wanted |
| Security advisory / CVE | lookup_advisory |
CVE IDs, advisory IDs, product vulnerability lookup |
| Exact hardware datasheet spec | lookup_hardware_specs |
"CX6300 switching capacity", "EX4400 PoE budget", "AP-635 specs" — curated catalog, not a document search |
| Exact AOS-CX release comparison | compare_aoscx_releases |
"what changed on CX 6100 from 10.13 to 10.16" — structured feature and release-note delta |
Follow-up questions and comparisons
Short follow-ups such as "what about 10.16 code?" are not standalone
questions. Preserve the prior product, platform, and comparison target, then
rewrite the follow-up into a standalone retrieval query before calling
ask_docs. Pass the same bounded summary in context when using the router,
for example:
{
"query": "what about 10.16 code?",
"context": "Comparing Juniper EX4000 with Aruba CX 6100; the question is about AOS-CX software support and VSF."
}
For hardware comparisons, retrieve exact model facts with
lookup_hardware_specs first. For AOS-CX version questions such as CX 6100
on 10.16, use compare_aoscx_releases with explicit platform,
from_version, and to_version; use ask_docs for explanatory prose around
the result. Do not infer an equivalence from product names alone.
Source filters for ask_docs / search_docs
Narrow with source= when the topic is clearly vendor-specific:
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.
- 5d ago First seen · 220 lines · 133 tokens per session scan A 8ef8602d668e
network-docs is a skill published in the GitHub repository secure-ssid/hpe-networking-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 133 tokens to every session and 3,222 once invoked, about $0.0007 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
planning-and-task-breakdown
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.
ue-mcp-epic-routing
Use when deciding between ue-mcp's native category actions and Epic's wrapped ToolsetRegistry tools (the epic actions, incl. the Blueprint graph DSL) for a task in Unreal. Pulls in when authoring Blueprint graph bodies, or any time both a native action and an epic action could do the job and you need to pick.
mcp-google-map-project
Project knowledge for developing and maintaining @cablate/mcp-google-map. Architecture, Google Maps API guide, GIS domain knowledge, and design decisions. Read this skill to onboard onto the project or make informed development decisions.