agentleFS
Lukk17Lukk17/agent-standards/.agents/skills/asus-router/SKILL.md

asus-router

Skill1 starsChanged 8 days agoMITView on GitHub

Working on an ASUS router over SSH from an agent, read only unless the owner approves one exact change: stock Asuswrt and Merlin, SSH key access, the system log, WAN and PPPoE state, and telling a link drop from an ISP outage. Use when the user says "let the agent into my router", "read the router log" or "why does the internet drop". Not for a Proxmox host behind the router, use `proxmox`.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before a change, say what it changes, the worst case, and the exact command that undoes it, then wait.

    line 53
  2. Very specific:

    Never run nvram show or nvram getall unfiltered and never print a value that holds a secret: the PPPoE password, a Wi-Fi key, the …

    line 54
  3. Very specific:

    Keep writes off the flash.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

ASUS Router Administration

How an agent reads an ASUS router over SSH without a password, and how a change the owner approved is done. The agent logs in with an SSH key as the router's administrator, which is root on the router. So the key can change anything, and the rules below are all that keeps the agent to reading. Stock Asuswrt and Asuswrt-Merlin share the SSH server, the system log and the WAN code, and every topic file says where Merlin differs.

Written for stock Asuswrt on the 388 and 102 firmware branches, on Wi-Fi 6 and 6E models such as the GT-AX6000, and Asuswrt-Merlin where it differs. Tool names and log texts were read in an unpacked stock firmware image for the GT-AX6000, never run, and in the Asuswrt-Merlin source and wiki and the ASUS FAQ pages named in each topic file. The image carries Dropbear, BusyBox, ip, ethctl and ethtool, though the tested router below had no ethtool. The owner tested part of it on a GT-AX6000 with stock firmware whose nvram get buildno printed 386: the SSH login with an ed25519 key, the log files, the nvram get reads, the PPP options, the log lines of PPPoE session drops, the WAN port link, the interfaces, routes and counters, and ping and traceroute from the router. Those commands and lines are marked VERIFIED with that build named. Every other command that runs on a router is UNVERIFIED until it is tested on a real one.

You are about toOpen
Turn SSH on, choose and paste the key, fill the env file, connect, take the key backssh-access.md
Read the system log, the WAN type, the interface names, the WAN port link, the uptime, ping from the routerreading-state.md
Open the ONT management page from the LAN while the WAN runs PPPoEont-access.md
Explain an internet drop: a WAN link drop, a PPPoE session drop, or an outage at the ISPtroubleshooting-drops.md

Facts about one setup

The router address, the administrator user name, the SSH port, the ONT address, the public IP and the PPPoE user name of a real setup belong in the owner's own notes, for example MACHINE.md next to the global AGENTS.md, never in this skill and never in a shared repository. Every example uses placeholders in angle brackets: <router-ip>, <router-admin-user>, <ssh-port>, <wan-ifname>, <ont-ip>, <ont-subnet>, <wan-side-ip>.


When to activate

  • Giving an agent SSH access to an ASUS router, or taking it back
  • Reading the router's system log, its WAN state or its uptime
  • An internet connection that drops now and then, and the question of whose fault it is
  • An ISP optical terminal or modem whose web page cannot be reached from the LAN
  • A change on the router that the owner asked for, such as a persistent ONT route on Merlin
  • Also covers stock Asuswrt on Wi-Fi 6 and 6E models such as the GT-AX6000, and Asuswrt-Merlin where it differs. SSH on the LAN only with an ed25519 key and no password login, the env file keys ASUS_ROUTER_SSH, ASUS_ROUTER_SSH_PORT and HOMELAB_SSH_KEY, taking the key back, the system log in /tmp/syslog.log or /jffs/syslog.log, WAN link, PPPoE and DHCP lines in the log, nvram get for the WAN type and interfaces, the WAN port link, ping from the router, reaching the ONT page from the LAN while the WAN runs PPPoE, and telling a WAN link drop from an ISP outage
  • The user says "is the WAN PPPoE or DHCP", "I cannot open the ONT page" or "was it the cable or the ISP"

When not to activate

  • A Proxmox host or a virtual machine behind the router, use proxmox
  • A service inside the home lab, such as Home Assistant or Syncthing, use home-assistant or syncthing
  • The network settings of one client machine, use windows, macos, arch-linux or cachyos
  • Judging whether an open port, a key or a firewall rule is acceptable, use the security-auditor agent
  • A script that wraps these commands on the agent's own machine, use bash or powershell

Hard rules

  1. The agent logs in with a key only: Enable SSH set to LAN only, Allow Password Login set to No, and the key in Authorized Keys. Never LAN & WAN, and the agent never gets the router password.
  2. The agent only reads. Without the owner's explicit yes for that exact change, it never runs reboot, a firmware update, nvram set, nvram unset or nvram commit, a factory reset, service restart_<name> or service stop_<name>, a change to Wi-Fi or WAN settings, an ip, ifconfig, route or iptables command that changes state, or a write under /jffs. One yes covers one change.
  3. Before a change, say what it changes, the worst case, and the exact command that undoes it, then wait. A change to the WAN, the firewall or SSH itself can cut the agent off, so name that case too.
  4. Never run nvram show or nvram getall unfiltered and never print a value that holds a secret: the PPPoE password, a Wi-Fi key, the administrator password, a VPN key. Read named values with nvram get <name>.
  5. The private key stays on the agent's machine, in ~/.ssh, and is passed with -i. Only the public key goes into the router. Never print the private key or the env file.
  6. Keep writes off the flash. A ping log or a capture goes to /tmp on the router, which is memory, or better to a machine in the LAN, never to /jffs.
  7. Read the log before it rotates away. The log file is small and keeps one older copy, so copy the lines you need into the agent's workspace right after reading them, and filter and count them there, because the router's BusyBox lacks tools such as uniq.
  8. A claim that the ISP is at fault needs the log lines and the ping log that show it, with their times, as troubleshooting-drops.md explains.
  9. Check the router's time zone rule and the clock offset of each kind of log line before you match it against anything else, and again after each change of summer or winter time. On build 386 the pppd lines ran one hour behind the router's own date in summer (2026-10-23), while other lines of the same event did not, and matched it in winter (2026-11-06).

Related skills

  • proxmox owns the Proxmox host and its virtual machines behind the router
  • home-assistant owns Home Assistant, which can also watch the router
  • The security-auditor agent owns judging an exposed port, a key or a firewall rule
  • bash and powershell own scripts on the agent's machine that wrap these commands
  • windows, macos, arch-linux and cachyos own the client machines on the LAN

Checklist

  • SSH runs on the LAN only, password login is off, and the agent's public key is in Authorized Keys
  • The env file holds ASUS_ROUTER_SSH, ASUS_ROUTER_SSH_PORT and HOMELAB_SSH_KEY, sits outside every repository, and is readable only by the owner
  • The first connection stored the router's host key, and BatchMode=yes connects with no prompt
  • The firmware version was read with nvram get firmver, nvram get buildno and nvram get extendno before a recipe was applied
  • No nvram show, no secret printed, no write under /jffs
  • Every change had its own yes after the worst case and the undo command were stated
  • The log lines and the ping log behind a diagnosis were copied out with their times
  • Every router command marked UNVERIFIED stays marked until it ran on a real router

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.