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 tikoci/routeros-skills --skill routeros-sniffergit clone --depth 1 https://github.com/tikoci/routeros-skillsWrote 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/tikoci/routeros-skills/routeros-sniffer)<a href="https://agentmods.dev/skills/tikoci/routeros-skills/routeros-sniffer"><img src="https://agentmods.dev/badge/skills/tikoci/routeros-skills/routeros-sniffer/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/tikoci/routeros-skills/routeros-sniffer"><img src="https://agentmods.dev/badge/skills/tikoci/routeros-skills/routeros-sniffer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Data Exfiltration · line 181 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00107 | $0.02802 |
| Opus 5 | $0.00053 | $0.01401 |
| Sonnet 5 | $0.00021 | $0.00560 |
| Haiku 4.5 | $0.00011 | $0.00280 |
Grade A, and why
routeros-sniffer scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -u admin: -X POST http://<router-ip>/rest/tool/sniffer/set \ Copies of this mod
1 near-identical copy found in the catalogue:
- routeros-sniffer — 100% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RouterOS Packet Capture & TZSP Streaming
RouterOS has a built-in packet sniffer (/tool/sniffer) and firewall mangle actions that can mirror traffic — either saving to a file on the router or streaming live to a remote host via TZSP (TaZmen Sniffer Protocol). This is the primary way to capture packets on RouterOS since standard tools like tcpdump do not exist (see routeros-fundamentals skill).
Why This Matters for Agents
When debugging any network protocol issue on RouterOS, agents should know they can:
- Stream live packets from the router to the host machine via TZSP — no hardware needed if using a CHR VM
- Save pcap/pcapng files on the router's flash and download them for analysis
- Use firewall mangle rules for surgical, per-flow packet mirroring without touching the sniffer config
Combined with a QEMU CHR instance (see routeros-qemu-chr skill), this gives agents a complete packet-level debugging workflow with zero physical hardware.
Method 1: /tool/sniffer (Full Capture Tool)
The built-in sniffer captures packets on specified interfaces with extensive filtering. It supports three independent output modes that can be combined:
| Output | Setting | Notes |
|---|---|---|
| Memory buffer | (always on) | Viewable via quick, packet, protocol, host, connection submenus. Packets available for 10 minutes |
| File on flash | file-name=capture.pcap |
PCAPNG format since RouterOS 7.20 |
| TZSP stream | streaming-enabled=yes |
UDP to streaming-server on streaming-port (default 37008) |
Live TZSP Streaming
# Configure sniffer to stream via TZSP to a remote host
/tool/sniffer
set streaming-enabled=yes streaming-server=<RECEIVER-IP>:37008
# Optional: filter to a specific interface or protocol
set filter-interface=ether1
set filter-ip-protocol=icmp
# Start capture (runs until stopped or router reboots)
/tool/sniffer/start
# Stop when done
/tool/sniffer/stop
The receiver host runs Wireshark, tshark, or another TZSP-capable tool (see TZSP receivers reference).
What ships with it
1 file 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.
- 12d ago First seen · 243 lines · 107 tokens per session scan A 3e947f12ba70
routeros-sniffer is a skill published in the GitHub repository tikoci/routeros-skills (58 stars, last pushed 1mo ago), licensed MIT. It adds 107 tokens to every session and 2,802 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
autonomous-bug-fix
Reproduces, diagnoses, fixes, and verifies bugs unaided.
debugging
Systematic root-cause investigation for hard bugs.
tia-doctor
Manual, read-only prerequisite probe for TIA Portal V21 and its modular Openness API, with optional Python TIA Scripting and TIA MCP checks.
8051-mcu-debug
Use when debugging 8051-compatible microcontrollers, 51 MCU firmware, STC download issues, Keil C51 projects, interrupts, timers, UART, or startup failures.
cortex-m-debug
Use when debugging Cortex-M microcontrollers, firmware bring-up, SWD/JTAG sessions, faults, startup code, or flashing failures.
firmware-boot-chain
Use when building or debugging a firmware and boot chain (RISC-V SBI, UEFI, ACPI, a bootloader handoff like Limine to an OS) or adding measured boot with a TPM, and a stage fails to hand off to the next.