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-backupgit 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-backup)<a href="https://agentmods.dev/skills/magnus919/agent-skills/headscale-backup"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/headscale-backup/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-backup"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/headscale-backup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.00758 |
| Opus 5 | $0.00025 | $0.00379 |
| Sonnet 5 | $0.00010 | $0.00152 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
headscale-backup 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 7d 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.
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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
headscale-backup
Overview
Headscale state is stored in SQLite (its database), config.yaml, policy.json, and TLS certificates. Regular backups are critical before upgrades, as database corruption or misconfiguration can result in complete loss of node registration and routing state. This skill provides three scripts covering the full lifecycle: backup, restore, and migration.
Backup Contents
A complete backup tarball includes:
- SQLite DB — Full node state, users, routes, pre-auth keys, API keys
config.yaml— Headscale server configurationpolicy.json— ACL policy file (if present)- Certs and keys — TLS certificate, private key, and node private key (
/var/lib/headscale/) - DERP map — DERP configuration file (if customized)
Backup Methods
sqlite3 .backup(recommended) — Safe for live databases; uses SQLite online backup API. This is whaths-backup.shuses.- File copy (
cp) — Requires stopping headscale first to avoid WAL corruption.
Restore
- Stop headscale service
- Restore files from backup tarball
- Start headscale service
- Verify with a health check or
headscale nodes list
Migration
- Backup on source host (or use an existing backup)
rsyncorscpthe backup tarball to the target host- Set up headscale on the target (same version)
- Restore from backup on target
- Update DNS to point to the new server
- Verify clients reconnect
Version Compatibility
Source and target headscale versions should match exactly. Restoring a database from a different headscale version may cause schema migration failures or data corruption. Check versions with headscale version before migrating.
Automated Backups (Cron)
Set up a daily cron job:
0 2 * * * /path/to/hs-backup.sh --auto --output-dir /backups/headscale/
Gotchas
- SQLite WAL mode:
sqlite3 .backupis safe;cpof the database file while headscale is running will produce a corrupt copy. - Version mismatch: Restoring to a different headscale version may break schema migrations.
- Node keys: If node keys change, all nodes must re-authenticate.
- API keys: API keys are stored hashed in the database; restoring a DB backup does not recover the original key secrets — regenerate them with
headscale apikeys create. - Pre-auth keys: Pre-auth keys are restored along with the database, but if they've expired they won't work.
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.
- 7d ago First seen · 82 lines · 50 tokens per session scan A 5df6d26f24f6
headscale-backup is a skill published in the GitHub repository magnus919/agent-skills (76 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 758 once invoked, about $0.0003 per session on Opus 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.
Other skills, from other repositories
routine
Manage CocoRoutine Snowflake task scheduling. Usage: $routine list, $routine schedule --cadence , $routine disable , $routine delete .
terraform-expert
Expert-level Terraform infrastructure as code, modules, state management, and production best practices. Use when the user mentions infrastructure as code, devops, or automation, or when the task involves Terraform Basics, Resource Management, Modules, or State Management.
floom
Create, run, and manage Floom AI workers — cloud automations that run on a schedule or a trigger and report back. Reach for this whenever the user wants something to happen repeatedly or in the background rather than a one-off script: a recurring task, "every day / every hour / every week", "schedule this", "run it on…
bridge-health
Quick health check on the bridge daemon (CEO machine + any exec mirrors). Surfaces heartbeat staleness, version drift, active sessions, and the Phase 1 to Phase 2 adoption gate metrics. Use when the dashboard feels stale, the sync-pill is red, the daemon may have crashed, or before a /push-updates that changes daemon…
control-plane-ops
Operar o control-plane local-first do agents-lab com board canônico, long-runs bounded, handoff/checkpoint, rollout/rollback e espelhos externos sem perder governança.
gandi
Gère les domaines, DNS et emails via l'API Gandi v5. Permet de lister les domaines, consulter/modifier les enregistrements DNS, gérer les boîtes mail et configurer les redirections.