Command parsing failure in leanrea's Router due to Markdown escaping of pipe characters.

The Router in `leanrea/SKILL.md` is a Markdown table, so the pipes inside its commands are escaped as `\|`. GitHub renders that as `|`, but an agent reads SKILL.md as raw text and copies the backslash with the command. Nine commands in six rows break that way.

Shell pipes become arguments to the first command:

```
$ strings -a T \| rg -o '/rustc/[0-9a-f]{40}' \| sort -u
strings: invalid option -- 'u'
$ rg -uu -o '"[a-z]+:[a-z0-9:-]+"' X \| sort -u
rg: |: No such file or directory (os error 2)
```

Regex alternations match a literal `|`, so they find nothing:

```
$ rg -c 'bl\|call\|literal\|cmp' dis.txt # 0
$ rg -c 'bl|call|literal|cmp' dis.txt # 79
```

The same goes for `'LC_(RPATH\|BUILD_VERSION)'`. And jq rejects its filter:

```
$ jq -r '.log.entries[].request \| .method+" "+.url' t.har
jq: error: syntax error, unexpected INVALID_CHARACTER
```

Affected: the Electron `sort -u` command, the Mach-O `otool -l` line, the Native code `awk ... | rg` line, both Go fallbacks, both Rust `strings` lines, and the pcap/HAR `tshark` and `jq` lines.

The Electron row also has the opposite problem. Its long IPC `rg` regex uses unescaped `|`, which splits the table cell when GitHub renders it.

Tested in bash on Linux with ripgrep 14.1.1, jq 1.8.1 and GNU binutils, on real binaries and a small HAR file.