Borrowing it
Nothing to install: this file belongs to Mats2208/MCP-Packet-Tracer. 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/Mats2208/MCP-Packet-Tracer/main/AGENTS.mdgit 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/instructions/mats2208/mcp-packet-tracer/agents-md)<a href="https://agentmods.dev/instructions/mats2208/mcp-packet-tracer/agents-md"><img src="https://agentmods.dev/badge/instructions/mats2208/mcp-packet-tracer/agents-md/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/instructions/mats2208/mcp-packet-tracer/agents-md"><img src="https://agentmods.dev/badge/instructions/mats2208/mcp-packet-tracer/agents-md.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.01314 | $0.01314 |
| Opus 5.5 | $0.00526 | $0.00526 |
| Sonnet 5.5 | $0.00263 | $0.00263 |
| Haiku 4.5 | $0.00131 | $0.00131 |
Grade A, and why
MCP-Packet-Tracer 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 9d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Notes for coding agents working in this repo. Read this before changing anything
under src/.
What this is
An MCP server that automates Cisco Packet Tracer. It plans network topologies, validates them, generates JavaScript for PT's script engine and IOS CLI config for the devices, and can push all of it into a running copy of Packet Tracer over a local HTTP bridge.
Language
Write everything in the repo in English: code, comments, docstrings, tool descriptions, user-facing messages, tests, docs and commit messages. This keeps the project usable by anyone, whatever their language. Talk to your user in their preferred language — only what you write into the repo is English.
Build and test
pip install -e ".[test]"
python -m pytest # from the repo root, no PT required
There is no linter or formatter configured. Match the surrounding style: type
hints on public functions, from __future__ import annotations at the top,
comments in English (see Language above).
Layout
| Path | What lives there |
|---|---|
src/packet_tracer_mcp/domain/ |
Pydantic models, validation rules, planning services |
src/packet_tracer_mcp/application/ |
Use cases: rules + generators, dependencies injected |
src/packet_tracer_mcp/infrastructure/ |
Generators, executors, the HTTP + file bridges, device catalog |
src/packet_tracer_mcp/adapters/mcp/ |
tools/<topic>.py — 62 tools, one register(mcp, ctx) each, run by tool_registry.py; bridge_context.py — the shared BridgeContext; device_panel_tools.py + desktop_service_tools.py — the 17 device-panel tools; prompt_registry.py / resource_registry.py — prompts and resources (pt://guide) |
src/packet_tracer_mcp/infrastructure/ui/ |
UI mode: Win32 + UI Automation presenter that opens/captures device windows (Windows only, [ui] extra) |
EXTENSION/script-engine/ |
Script-engine side of the extension. main.js is ours (tracked); the rest are PTBuilder reference copies (gitignored) |
EXTENSION/webview/ |
The MCP Control Center webview (index.html + interface.js) |
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.
- 9d ago Changed · +16 lines · +317 tokens per session bf748e9bad74
- 17d ago Changed 50de237f9fa6
- 1mo ago First seen · 83 lines · 997 tokens per session scan A 0bc991328610
MCP-Packet-Tracer AGENTS.md is an instructions file published in the GitHub repository Mats2208/MCP-Packet-Tracer (284 stars, last pushed 9d ago), licensed MIT. It adds 1,314 tokens to every session, about $0.0053 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 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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.