What is mikrotik-cli-probe?

A diagnostic tool for checking the raw command-line output returned by a MikroTik router over Telnet or other terminal-style connections. MikroTik is a maker of routers, and RouterOS is their router operating system.

Use it to debug tik4net Telnet, SSH terminal, MAC-Telnet, or WinBox command-line connections and inspect the bytes, prompts, and formatting the router actually sends.

It helps explain empty, garbled, or difficult-to-parse terminal output before troubleshooting the library that connects to the router. It can distinguish router behaviour from client or transport problems.

How danikf/tik4net configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to danikf/tik4net. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/danikf/tik4net/master/.claude/skills/mikrotik-cli-probe/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/danikf/tik4net

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/danikf/tik4net/mikrotik-cli-probe/github.svg)](https://agentmods.dev/skills/danikf/tik4net/mikrotik-cli-probe)

Your own site

<a href="https://agentmods.dev/skills/danikf/tik4net/mikrotik-cli-probe"><img src="https://agentmods.dev/badge/skills/danikf/tik4net/mikrotik-cli-probe/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/danikf/tik4net/mikrotik-cli-probe"><img src="https://agentmods.dev/badge/skills/danikf/tik4net/mikrotik-cli-probe.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 166 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,055 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00166	$0.02055
Opus 5.5	$0.00066	$0.00822
Sonnet 5.5	$0.00033	$0.00411
Haiku 4.5	$0.00017	$0.00205

Measured 2mo ago against content hash 48c804f691be, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mikrotik-cli-probe 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 2mo 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.

.claude/skills/mikrotik-cli-probe/SKILL.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MikroTik CLI probe (Telnet / PTY)

The binary API (mikrotik skill / mikrotik_call) is the right tool for normal queries. Use THIS skill when the question is specifically about the terminal/CLI layer: what RouterOS emits over a PTY, why a CLI command returns nothing, how to shape a command so its output is parseable, etc. This is the layer tik4net's CLI-based transports (tik4net/Cli/, tik4net/Telnet/) sit on.

Two ways to get terminal ground truth. The probe script below is the router-only view (no tik4net at all). To see the same raw bytes as tik4net itself sees them — through the actual transport, with the mepty pull cadence, VT100 answers and prompt/settle decisions the library makes — use mikrotik_call with traceLevel:'bytes' (channels telnet.sock, wbxcli.mepty, mactelnet.udp) and optionally includeRouterLog:true for the device-side log. That is the in-library equivalent of this probe and the faster first stop when the question is "what did our client do", not "what can the router do at all". See the mikrotik skill's Wire tracing & router-log debugging section. Reach for the standalone probe script when you need a reference implementation independent of tik4net.

Check which server answered. The MCP route runs a staged copy of the build output, so a trace can silently come from the server you had before your last build. Every answer names the assembly that produced it — mikrotik_call on a trailing --- MCP SERVER --- … built <timestamp> … line, mikrotik_cli_complete in its serverBuild property. If that timestamp predates your build, the trace is evidence about the OLD code; reconnect tik4net-mcp and take it again. The probe script has no such trap: it does not use the library at all, which is exactly why it stays the tie-breaker.

The probe script

Tools/probes/telnet-cli-probe.ps1 is a minimal, self-contained Telnet client that reproduces exactly what a correct PTY transport must do — Telnet IAC negotiation, VT100 cursor-probe answers, and login with change-password-nag dismissal — then prints the RAW bytes the router returns (ESC shown as \e, CR/LF as \r/\n). It deliberately does NOT use the tik4net library, so it gives you ground truth to compare the library against.

Read the full file on GitHub · 110 lines

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.

2mo ago First seen · 110 lines · 166 tokens per session scan A 48c804f691be

Subscribe to this mod's changes

mikrotik-cli-probe is a skill published in the GitHub repository danikf/tik4net (198 stars, last pushed yesterday), licensed Apache-2.0. It adds 166 tokens to every session and 2,055 once invoked, about $0.0007 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.

Debugging Hardware and IoT api-client c-sharp dotnet library mikrotik mikrotik-router

routeros-mac-telnet

MAC-Telnet protocol (MikroTik Layer-2 terminal/exec over UDP 20561) wire format, session handshake, and MD5 + MTWEI (EC-SRP) authentication. Use when: implementing or debugging a MAC-Telnet client/server, reaching a RouterOS device by MAC address without IP, parsing MAC-Telnet packets, understanding the WinBox-style…

tikoci/routeros-skills · 141 tokens

routeros-syntax-inspection

Inspecting and validating RouterOS command/script syntax against a live device via /console/inspect (highlight, completion, syntax, child) and :parse IL. Use when: validating RouterOS commands before execution, explaining or linting RouterOS scripts, building syntax-aware tooling (LSP servers, validators, agent…

tikoci/routeros-skills · 111 tokens

routeros-sniffer

RouterOS packet capture and TZSP streaming for protocol debugging. Use when: capturing packets on RouterOS, setting up /tool/sniffer, streaming live traffic via TZSP, using firewall mangle action=sniff-tzsp, debugging network protocols on MikroTik, receiving TZSP with Wireshark or tshark, saving pcap files from…

tikoci/routeros-skills · 107 tokens

gke-ai-troubleshooting-tpu-dynamic-slices-monitoring

Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use…

google/skills · 107 tokens

gke-ai-troubleshooting-tpu-vbar-oom

Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…

google/skills · 125 tokens

doca-flow

DOCA Flow packet steering on NVIDIA NICs/DPUs, linked into a C application: match/action pipes, ports, representors, forwarding, hairpin, counters. Trigger on packet steering, classifier, rule-matching, representor, hairpin or 5-tuple-to-queue questions even when "DOCA Flow" is not named. Also covers pipe validation…

NVIDIA/skills · 224 tokens

tik4net: Skill for Claude Code