headscale-node-lifecycle

headscale-node-lifecycle is a skill for Claude Code from magnus919/agent-skills. It costs 55 tokens per session (1,219 once invoked), scanned A, original, MIT.

Instructions for managing devices, called nodes, throughout their life in a Headscale private network. This includes registering, approving, tagging, listing, and removing devices.

In plain words
What is it for?
Use it to create authentication keys, enroll devices, assign tags, inspect the device list, or decommission nodes.
Why use it?
It keeps device access and identity organized, including devices added automatically or used temporarily by automation.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the tailscale plugin — 8 skills shipped together

Good fit Use it to create authentication keys, enroll devices, assign tags, inspect the device list, or decommission nodes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/magnus919/agent-skills/headscale-node-lifecycle
Install

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.

Any agent
npx skills add magnus919/agent-skills --skill headscale-node-lifecycle
Clone the repo
git clone --depth 1 https://github.com/magnus919/agent-skills

Made for: Claude Code.

Or install tailscale, the plugin that ships this one along with the rest of its 8 skills.

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.

agentmods badge for headscale-node-lifecycle

README.md
[![agentmods](https://agentmods.dev/badge/skills/magnus919/agent-skills/headscale-node-lifecycle/github.svg)](https://agentmods.dev/skills/magnus919/agent-skills/headscale-node-lifecycle)
Your own site
<a href="https://agentmods.dev/skills/magnus919/agent-skills/headscale-node-lifecycle"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/headscale-node-lifecycle/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.

agentmods 80×15 button for headscale-node-lifecycle

Your own site · 80×15
<a href="https://agentmods.dev/skills/magnus919/agent-skills/headscale-node-lifecycle"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/headscale-node-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,219 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Tool Misuse · line 66
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • medium Excessive Agency · line 38
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00055 $0.01219
Opus 5.5 $0.00022 $0.00488
Sonnet 5.5 $0.00011 $0.00244
Haiku 4.5 $0.00006 $0.00122

Measured 2mo ago against content hash 537693565776, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

headscale-node-lifecycle 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 2mo ago.

The scan reads SKILL.md. This mod also ships 4 executable files (scripts/hs-approve-nodes.sh, scripts/hs-create-authkey.sh, scripts/hs-list-nodes.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

tailscale/skills/headscale-node-lifecycle/SKILL.md · 135 lines

How it starts

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

headscale-node-lifecycle

Overview

Headscale manages nodes in a tailnet with two identity models:

  • Personal nodes — registered under a specific user account (e.g. yourname@domain). The node key is tied to that user's identity.
  • Tagged nodes — belong to the special tagged-devices user (created automatically by Headscale). These nodes are identified by one or more tags (e.g. tag:webserver, tag:monitoring) and are typically used for infrastructure service nodes.

Registration happens through:

  1. Web auth — user visits a URL to authenticate with an OIDC/OAuth provider
  2. Pre-authenticated key (auth key) — a one-time or reusable key generated by the admin that embeds tags, user, and expiry
  3. CLI / API — direct node registration via headscale commands or REST API calls

Pre-authenticated Keys

Auth keys streamline automated node registration. Key attributes:

Parameter Description
Expiration Default: 1 hour. Use 0 for no expiry (not recommended).
Reusable Single-use by default. Mark reusable for fleet provisioning.
Ephemeral Ephemeral nodes are removed from the tailnet when they disconnect. Perfect for CI runners and ephemeral workloads.
Tags Assign tags to create a tagged node automatically.

Node Registration

  • Personal nodes: Create an auth key for a user → run tailscale up --auth-key=<key> on the device → approve in Headscale if registration is open.
  • Tagged nodes: Create an auth key with --tags → run tailscale up --auth-key=<key> → the node is auto-approved and tagged.

Node Listing

List nodes filtered by user, tag, or online status. Output includes:

  • Node ID
  • Name (hostname)
  • Tailscale IP address(es)
  • Assigned tags
  • User/owner
  • Online/offline status
  • Last seen timestamp
  • Operating system
  • Tailscale client version

Read the full file on GitHub · 135 lines

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. 2mo ago First seen · 135 lines · 55 tokens per session scan A 537693565776

Subscribe to this mod's changes

headscale-node-lifecycle is a skill published in the GitHub repository magnus919/agent-skills (166 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 1,219 once invoked, about $0.0002 per session on Opus 5.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-09-03.

Related

headscale-node-lifecycle compared with skills from other repositories

headscale-node-lifecycle next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
headscale-node-lifecyclemagnus919/agent-skillsSkill1662d agoMITA55Claude Code
cocoreviewSnowflake-Labs/cocoplusSkill727todayMITA57Claude Code
discussSnowflake-Labs/cocoplusSkill727todayMITA54Claude Code
cocoharvestSnowflake-Labs/cocoplusSkill727todayMITA68Claude Code
cocoscoutSnowflake-Labs/cocoplusSkill727todayMITA59Claude Code
bloomSnowflake-Labs/cocoplusSkill727todayMITA47Claude Code
klatchSnowflake-Labs/cocoplusSkill727todayMITA54Claude Code