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 magnus919/agent-skills --skill headscale-deploygit clone --depth 1 https://github.com/magnus919/agent-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/magnus919/agent-skills/headscale-deploy)<a href="https://agentmods.dev/skills/magnus919/agent-skills/headscale-deploy"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/headscale-deploy/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/magnus919/agent-skills/headscale-deploy"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/headscale-deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
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 →
- medium Privilege Escalation · line 27 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Rogue Agent · line 33 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00043 | $0.01247 |
| Opus 5 | $0.00022 | $0.00624 |
| Sonnet 5 | $0.00009 | $0.00249 |
| Haiku 4.5 | $0.00004 | $0.00125 |
Grade B, and why
headscale-deploy scanned grade B with 2 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 5d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Root or sudo access on the target machine Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://headscale.example.com/health How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
headscale-deploy
Overview
Headscale is an open-source, self-hosted implementation of the Tailscale control server. It allows you to run your own coordination plane for WireGuard-based mesh networking, giving you full control over your tailnet without relying on Tailscale's SaaS infrastructure. The Tailscale client connects to Headscale transparently — no client modifications needed.
Use this skill to deploy Headscale from scratch, configure server settings, manage DERP relay infrastructure, and diagnose deployment issues.
Prerequisites
- Linux server (x86_64 or aarch64) or Docker host with compose support
- DNS record pointing to the server (A/AAAA record for
server_url) - Ports 80/443 accessible from the internet (or your tailnet's ingress point)
- Port 3478/udp for STUN (optional, needed for NAT traversal)
- Root or sudo access on the target machine
Deployment Methods
Docker Compose (Recommended)
The fastest and most maintainable approach. Use install-headscale.sh with --docker flag to generate a compose file and systemd drop-in, or create manually:
version: "3.9"
services:
headscale:
image: headscale/headscale:latest
container_name: headscale
restart: unless-stopped
ports:
- "8080:8080"
- "3478:3478/udp"
volumes:
- ./data:/var/lib/headscale
- ./config:/etc/headscale
command: headscale serve
Binary Install
Direct binary installation on the host for lightweight or container-free environments. The install-headscale.sh script handles:
- Detecting platform (linux/amd64, linux/arm64)
- Downloading the release tarball from GitHub
- Installing the binary to
/usr/local/bin - Creating the
headscalesystem user - Writing a systemd unit file
- Creating default config at
/etc/headscale/config.yaml
Configuration
Key config.yaml options:
| Option | Description | Example |
|---|---|---|
server_url |
Public URL of your Headscale instance | https://headscale.example.com:443 |
listen_addr |
Local bind address | 0.0.0.0:8080 |
metrics_listen_addr |
Prometheus metrics endpoint | 127.0.0.1:9090 |
dns_config.base_domain |
MagicDNS domain suffix | example.com |
dns_config.magic_dns |
Enable MagicDNS | true |
derp.server.enabled |
Enable embedded DERP relay | false |
derp.server.region_id |
Numeric region ID | 999 |
derp.server.region_name |
Human-readable region name | "my-headscale" |
derp.urls |
External DERP map URLs | [] |
db_type |
Database backend: sqlite3 or postgres |
sqlite3 |
tls_letsencrypt_hostname |
Auto TLS via Let's Encrypt | "" |
tls_cert_path / tls_key_path |
Manual TLS cert paths | "" |
What ships with it
5 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.
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.
- 5d ago First seen · 125 lines · 43 tokens per session scan B 8701cac03a27
headscale-deploy is a skill published in the GitHub repository magnus919/agent-skills (75 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,247 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.
docker-patterns
Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…