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 skills add Mats2208/MCP-Packet-Tracer --skill skillgit clone --depth 1 https://github.com/Mats2208/MCP-Packet-TracerWrote 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/mats2208/mcp-packet-tracer/skill)<a href="https://agentmods.dev/skills/mats2208/mcp-packet-tracer/skill"><img src="https://agentmods.dev/badge/skills/mats2208/mcp-packet-tracer/skill/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/skills/mats2208/mcp-packet-tracer/skill"><img src="https://agentmods.dev/badge/skills/mats2208/mcp-packet-tracer/skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Memory Poisoning · line 88 Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.Fix: Implement context-window management that detects and rejects padding or stuffing attempts. Prioritize system instructions over user-injected content.
- medium Excessive Agency · line 353 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00139 | $0.02398 |
| Opus 5.5 | $0.00056 | $0.00959 |
| Sonnet 5.5 | $0.00028 | $0.00480 |
| Haiku 4.5 | $0.00014 | $0.00240 |
Grade A, and why
packet-tracer 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 2d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Packet Tracer MCP — operating guide
A Model Context Protocol server (packet-tracer) that drives Cisco Packet Tracer: plan a
topology, validate it, generate IOS/PTBuilder artifacts, and live-deploy into a running PT
over an HTTP bridge. The pt_* tools are your only interface — plus raw JS via pt_send_raw.
⛔ Prime directive: DISCOVER, never invent
The single biggest failure mode for a model driving this MCP is guessing — a model name, a port name, a slot id, a cable type, a module name, or a Script-Engine API method. Every one of these is discoverable, and a wrong guess either fails validation or (for raw JS) freezes Packet Tracer (see the modal-freeze rule below).
Rules:
- If you did not read it from a tool result, an MCP resource, or this skill, you do not know it — look it up first.
- Before planning/deploying:
pt_list_devices,pt_list_templates,pt_get_device_details, andpt_list_modules(if installing modules). - Before any raw JS: use only methods in the Verified Script-Engine API table below. If you need something not listed, probe it inside a try/catch before relying on it.
- After every mutation, read back with
pt_query_topology/pt_export_topologyand confirm. - When something isn't in the catalog, say so — do not fabricate a device/module to fill the gap.
The bridge (mental model)
LLM ──▶ MCP server ──▶ HTTP bridge :54321 ──▶ MCP Control Center (PT extension) ──▶ PT Script Engine
- The MCP queues JS at
:54321; the PT extension polls/nextevery 500 ms and runs each command via$se('runCode', …)in PT's Script Engine, posting results back to/result. XMLHttpRequestdoes NOT exist in the Script Engine (only in the extension webview). That's why all I/O goes through the bridge.- Confirm the link first with
pt_bridge_status→ must say "ACTIVE and CONNECTED". If "NOT connected", the user opens Extensions → MCP BUILDER in PT (or dismisses a stuck error modal).
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago Changed · +10 lines 05b20b5c0568
- 13d ago Changed · -301 lines f02280a4cc65
- 21d ago Changed · +24 lines 7523bec4fe9b
- 2mo ago First seen · 396 lines · 139 tokens per session scan A 4354178e2230
packet-tracer is a skill published in the GitHub repository Mats2208/MCP-Packet-Tracer (312 stars, last pushed 3d ago), licensed MIT. It adds 139 tokens to every session and 2,398 once invoked, about $0.0006 per session on Opus 5.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 skills, from other repositories
linux-networking
Linux networking expert for iptables, nftables, routing, DNS, and network troubleshooting.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
python-debugpy
Debug Python: pdb REPL + debugpy remote (DAP).
sglang-diffusion-benchmark-profile
Use when benchmarking denoise latency or profiling a diffusion bottleneck in SGLang.