headscale-routing SKILL.md skillA
headscale-routing from magnus919/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add magnus919/agent-skills/headscale-routing@git:20260814.0a7c6b9Pins git:20260814.0a7c6b9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- magnus919/agent-skills
- Path
tailscale/skills/headscale-routing/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260814.0a7c6b9, committed Aug 14, 2026
- First version recorded
- Aug 14, 2026
- Size
- 4,983 bytes
- Repository stars
- 166
- License
- MIT
Configure subnet routers and exit nodes in a Headscale tailnet to extend.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# headscale-routing ## Overview Subnet routers extend a tailnet to non-Tailscale devices (printers, NAS boxes, IoT devices) by advertising the local LAN subnet routes through a gateway node. Exit nodes route all non-tailnet internet traffic through a home server, providing privacy on untrusted networks (coffee shop Wi-Fi, hotel networks, etc.). Headscale manages route approval centrally — routes must be advertised by the gateway node and then approved on the Headscale server before they become active. ## Subnet Router Setup 1. On the gateway node, advertise the LAN subnet: ```bash tailscale up --advertise-routes=192.168.1.0/24 ``` 2. On the Headscale server, approve the route: ```bash headscale routes approve -r <route-id> ``` 3. On client nodes that need to reach the subnet, enable route acceptance: ```bash tailscale up --accept-routes ``` ## Exit Node Setup 1. On the exit node, advertise it as an exit node: ```bash tailscale up --advertise-exit-node ``` 2. On the Headscale server, approve the exit node route. 3. On the client, select the exit node: ```bash tailscale set --exit-node=<node-name> ``` ## Auto-Approvers …
Read the whole file at its exact version.
How to install
mdr add magnus919/agent-skills/headscale-routing@sha256:6aaf3e548621eac3The line at the top of this page pins the label git:20260814.0a7c6b9, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_6qfylu7nvwbylbv6)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Aug 14, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260814.0a7c6b9 latest | 2026-08-14 | 0a7c6b9 | 4,983 B | A | view · diff |
| git:20260814.c0c7690 | 2026-08-14 | c0c7690 | 4,769 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4983 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
magnus919/agent-skills · 166 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6qfylu7nvwbylbv6 GET https://markdownregistry.com/api/v1/resolve?ref=magnus919/agent-skills/headscale-routing GET https://markdownregistry.com/api/v1/blob/6aaf3e548621eac36d95d690226cc22215dafac73855778151d8a52377d8cae6
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.