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-centrsgit 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-centrs)<a href="https://agentmods.dev/skills/tikoci/routeros-skills/routeros-centrs"><img src="https://agentmods.dev/badge/skills/tikoci/routeros-skills/routeros-centrs/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-centrs"><img src="https://agentmods.dev/badge/skills/tikoci/routeros-skills/routeros-centrs.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.00247 | $0.04083 |
| Opus 5.5 | $0.00099 | $0.01633 |
| Sonnet 5.5 | $0.00049 | $0.00817 |
| Haiku 4.5 | $0.00025 | $0.00408 |
Grade A, and why
routeros-centrs 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 24d 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.
description: "Use whenever a task touches a real MikroTik RouterOS device or CHR: reading or changing config, running a RouterOS CLI command non-interactively, checking a command is well-formed before sending it, moving How it starts
The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Driving RouterOS with centrs
What this is for
@tikoci/centrs is a friendly conduit to
RouterOS, not a configuration abstraction. You still speak RouterOS; centrs handles
the parts that are tedious and error-prone to do by hand:
- resolving
<router>to an address, credentials, port, and a protocol; - validating a RouterOS-shaped command before it runs;
- returning the same structured envelope whatever transport carried the call.
Validation and structured diagnostics are the product. Without them it would be a
worse curl.
Reach for centrs when you need to run a RouterOS command, read state, or move a file — from a shell script, a test, or an agent loop.
Don't reach for it when you need RouterOS documentation (use the rosetta MCP
or the routeros-fundamentals skill), or when you need to create the router itself
(use routeros-quickchr-cli from a shell, or routeros-quickchr for the TypeScript
library — centrs consumes a quickchr VM, it does not boot one).
Status:
0.1.xpreview under active development. The repo README publishes preview builds under npm'snexttag, so pin@nextrather than assuminglatesttracks them — confirm withnpm view @tikoci/centrs dist-tags. Expect breaking changes before 1.0 and exercise writes on lab or disposable targets first.docs/MATRIX.mdis the single source of truth for what works today; treat anything not green there as not-yet-shipped.
Install and first call
bunx @tikoci/centrs@next --help # no install
bun add @tikoci/centrs@next # library + local CLI
The offline analyzer needs no router and no credentials — it is the cheapest way to confirm centrs works at all:
bunx @tikoci/centrs@next explain '/ip/address print' --json
The loop: explain → run
This is the pattern centrs exists for. Analyze the command offline, then run it.
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.
- 24d ago Changed · +2 lines · +13 tokens per session 249a9df83004
- 25d ago First seen · 302 lines · 234 tokens per session scan A c666165d3e59
routeros-centrs is a skill published in the GitHub repository tikoci/routeros-skills (74 stars, last pushed yesterday), licensed MIT. It adds 247 tokens to every session and 4,083 once invoked, about $0.0010 per session on Opus 5.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-09-21.
Other skills, from other repositories
lab-hardware-cad
Designs custom laboratory hardware as parametric build123d models and exports fabrication artifacts as STEP, STL, and DXF files - microfluidic chips and molds, optomechanical mounts and breadboard adapters, cuvette and microplate holders, tube racks, animal-behavior rigs, and 3D-printed instrument fixtures. Use when a…
pylabrobot
Develops and reviews PyLabRobot lab-automation resources, liquid-handling plans, offline simulations, and supported-device integrations. Supports PyLabRobot protocols and API questions; keep physical execution behind an explicit operator safety gate.
pybamm
Simulates lithium-ion battery charge, discharge and rest experiments with PyBaMM, records parameter-set provenance, checks mesh and solver sensitivity, and compares predicted voltage curves with measured cycling data. Use for SPM or DFN electrochemical battery modeling, C-rate protocols, voltage cutoffs, parameter…
offensive-wifi
Wireless / 802.11 attack methodology for red team engagements and wireless security assessments. Covers monitor-mode setup, WPA/WPA2-PSK handshake capture and PMKID attacks, WPA3 SAE downgrade and Dragonblood, WPA-Enterprise (EAP) attacks (MSCHAPv2 cracking, EAP-TLS cert theft, evil-twin RADIUS), Karma / Known Beacons…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
offensive-iot
IoT and embedded device security testing methodology. Covers hardware reconnaissance (UART, JTAG, SWD, SPI flash, I2C EEPROM, eMMC chip-off), firmware acquisition (vendor portals, OTA capture, flash dump, binwalk extraction), firmware analysis (filesystem mounting, binary triage, hardcoded secrets, default credential…