tailscale-acl AGENTS.md

Repository-specific instructions for managing Tailscale access-control policies with GitOps, a practice of changing infrastructure through version-controlled files and automated workflows.

In plain words
What is it for?
Editing, validating, and deploying Tailscale ACL rules through GitHub Actions while preserving the repository’s conventions.
Why use it?
They explain the required policy file, project structure, and validation process for network access changes.

Instructions file for CodexOpenCode

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.

agentmods
npx agentmods add instructions/enuno/tailscale-acl/agents-md
Clone the repo
git clone --depth 1 https://github.com/enuno/tailscale-acl

Made for: Codex, OpenCode.

Per session 1,067 This file is loaded in full into every session.
When invoked 1,067 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.01067 $0.01067
Opus 5 $0.00534 $0.00534
Sonnet 5 $0.00213 $0.00213
Haiku 4.5 $0.00107 $0.00107

Measured 2d ago against content hash 5614f2fbd915, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tailscale-acl AGENTS.md 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 2d 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.

AGENTS.md · 144 lines

How it starts

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

AI Agent Instructions for Tailscale ACL Repository

Project Overview

This repository manages Tailscale Access Control Lists through GitOps methodology, enabling infrastructure-as-code for network security policies. The primary goal is maintaining secure, reliable, and auditable network access control.

Core Technologies

  • Tailscale: Zero-trust network access platform with WireGuard-based mesh networking
  • GitOps: Infrastructure management through Git workflows and automated deployment
  • HuJSON: Human-readable JSON format for ACL policies with comments and trailing commas
  • GitHub Actions: CI/CD pipeline for ACL validation and deployment

Repository Structure

Essential Files

  • policy.hujson: Main Tailscale ACL policy file (NEVER rename this file)
  • .github/workflows/tailscale.yml: GitHub Actions workflow for ACL synchronization
  • README.md: Project documentation and setup instructions

Configuration Files

  • .cursorrules, .clinerules: AI agent-specific configurations
  • .yamllint, .prettierrc: Code quality and formatting tools
  • .editorconfig: Cross-editor consistency settings
  • .gitignore: Git ignore patterns for clean repository

Development Workflow

1. ACL Policy Changes

  • Edit policy.hujson in feature branches only
  • Use HuJSON format with comments and trailing commas
  • Include test cases for all new access rules
  • Follow least privilege security principles

2. Git Workflow

# Create feature branch
git checkout -b feature/add-user-group

# Make changes to policy.hujson
# Commit with descriptive messages
git commit -m "feat: add engineering team access to production servers"

# Push and create pull request
git push origin feature/add-user-group

3. CI/CD Process

  • Pull requests trigger ACL validation (test action)
  • Merging to main triggers deployment (apply action)
  • Monitor GitHub Actions logs for deployment status
  • Failed deployments prevent policy updates

Tailscale ACL Best Practices

Read the full file on GitHub · 144 lines

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. 2d ago First seen · 144 lines · 1,067 tokens per session scan A 5614f2fbd915

Subscribe to this mod's changes

tailscale-acl AGENTS.md is an instructions file published in the GitHub repository enuno/tailscale-acl (5 stars, last pushed 9mo ago), licensed Apache-2.0. It adds 1,067 tokens to every session, about $0.0053 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-08-31.