What is mikrotik-replay?

A read-only tool for investigating past MikroTik slowdowns and outages by reviewing saved network measurements such as CPU use, memory, delay, traffic, and dropped connections.

Use it to investigate questions such as why the internet was slow two hours ago, find unusual measurements, and connect them into a likely chain of causes.

It helps explain what happened during an earlier time window, even when ordinary monitoring only shows the present. It can only investigate periods that were recorded beforehand.

How Syamsuddin/MikroCLAW configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Syamsuddin/MikroCLAW. 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/Syamsuddin/MikroCLAW/main/.claude/skills/mikrotik-replay/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/Syamsuddin/MikroCLAW

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/syamsuddin/mikroclaw/mikrotik-replay/github.svg)](https://agentmods.dev/skills/syamsuddin/mikroclaw/mikrotik-replay)

Your own site

<a href="https://agentmods.dev/skills/syamsuddin/mikroclaw/mikrotik-replay"><img src="https://agentmods.dev/badge/skills/syamsuddin/mikroclaw/mikrotik-replay/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/syamsuddin/mikroclaw/mikrotik-replay"><img src="https://agentmods.dev/badge/skills/syamsuddin/mikroclaw/mikrotik-replay.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 958 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.

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.00142	$0.00958
Opus 5	$0.00071	$0.00479
Sonnet 5	$0.00028	$0.00192
Haiku 4.5	$0.00014	$0.00096

Measured 10d ago against content hash 614009b022b4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

mikrotik-replay 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 10d 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-replay/SKILL.md · 59 lines

How it starts

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

MikroTik Replay — RCA Retrospektif

Menjawab pertanyaan paling sering operator — "kenapa tadi sore lemot?" — yang tak terjawab oleh monitoring present-tense. Membaca riwayat telemetri yang dipersist MikroCLAW Pulse pada jendela waktu yang diminta, menghitung statistik, dan menandai anomali untuk merekonstruksi rantai sebab. Read-only.

Prasyarat

Riwayat ditulis oleh MikroCLAW Pulse (uv run mikroclaw-web) tiap ~30 detik ke MIKROCLAW_STATE_DIR/history. Replay hanya bisa menjelaskan rentang waktu saat Pulse sedang berjalan. Bila kosong, sarankan menjalankan Pulse agar insiden berikutnya terekam.

Tool yang dipakai

mcp__mikroclaw__explain_incident — inti: ambil jendela [mulai_menit_lalu, selesai_menit_lalu], kembalikan metrik (min/max/mean/median per metrik), anomali[] deterministik (lonjakan RTT, timeout/outage, CPU tinggi berkelanjutan, lonjakan conntrack/drops), dan deret_ringkas.
(konteks live opsional) recent_logs untuk menautkan kejadian, ping/ traceroute untuk kondisi sekarang, firewall_connections untuk pelaku saat ini.

Prosedur

Tentukan jendela. Terjemahkan "tadi sore" / "2 jam lalu" menjadi mulai_menit_lalu/selesai_menit_lalu. Bila ragu, ambil rentang lebih lebar dulu lalu persempit.
Tarik telemetri. Panggil explain_incident. Periksa kosong (Pulse belum jalan?) dan keparahan_tertinggi.
Korelasikan anomali. Hubungkan lonjakan antar-metrik untuk menebak akar masalah — mis. "RTT internet 15→480ms BERSAMAAN conntrack melonjak 800→5000 & CPU 95% → satu host menjenuhkan conntrack (P2P), bukan gangguan ISP."
Tautkan ke log. Cek recent_logs untuk peristiwa di sekitar waktu itu (link down, DHCP, login).
Simpulkan & cegah. Beri akar masalah + saran agar tak terulang (mis. batasi conntrack per-IP, queue untuk host berat, alert).

Format laporan

## Replay — RCA 17:00–18:00
**Data:** 120 sampel · 🟠 2 anomali (tertinggi: warning)

**Anomali:**
- RTT internet melonjak ke 480ms (median 18ms) — saturasi link
- Conntrack melonjak ke 5.000 (median 800) — banyak sesi/flood

**Rekonstruksi:** ~17:32 conntrack & RTT naik bersamaan, CPU firewall ~95%.
Pola khas SATU klien membanjiri sesi (torrent). Bukan gangguan ISP.
**Saran:** batasi conntrack/queue untuk host tersebut; pasang alert dini.

Read the full file on GitHub · 59 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.

10d ago First seen · 59 lines · 142 tokens per session scan A 614009b022b4

Subscribe to this mod's changes

mikrotik-replay is a skill published in the GitHub repository Syamsuddin/MikroCLAW (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 142 tokens to every session and 958 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.

Debugging

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…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens

MikroCLAW: Skill for Claude Code