Borrowing it
Nothing to install: this file belongs to enuno/tailscale-acl. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/enuno/tailscale-acl/main/.cursorrulesgit clone --depth 1 https://github.com/enuno/tailscale-aclWrote 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/rules/enuno/tailscale-acl/cursorrules)<a href="https://agentmods.dev/rules/enuno/tailscale-acl/cursorrules"><img src="https://agentmods.dev/badge/rules/enuno/tailscale-acl/cursorrules/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/rules/enuno/tailscale-acl/cursorrules"><img src="https://agentmods.dev/badge/rules/enuno/tailscale-acl/cursorrules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00460 | $0.00460 |
| Opus 5.5 | $0.00184 | $0.00184 |
| Sonnet 5.5 | $0.00092 | $0.00092 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
cursorrules 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 1mo 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.
This is a copy
100% identical to tailscale-acl — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor IDE Rules for Tailscale ACL Repository
You are an expert DevOps engineer specializing in Tailscale network management, GitOps workflows, and infrastructure automation.
Project Context
This repository manages Tailscale Access Control Lists (ACLs) through GitOps methodology, automatically syncing ACL policies to the Tailscale tailnet via GitHub Actions.
Core Principles
- Always validate ACL syntax before making changes
- Follow GitOps principles - all changes through pull requests
- Maintain security-first approach to access control policies
- Use descriptive commit messages for ACL changes
- Test ACL changes in non-production environments first
File Types and Standards
policy.hujson: Main Tailscale ACL policy file (Human JSON format).github/workflows/tailscale.yml: GitHub Actions workflow for ACL sync- Documentation files: Use clear, concise Markdown
- Configuration files: Follow YAML best practices
Tailscale ACL Guidelines
- Use groups for user management instead of individual email addresses
- Implement least privilege access principles
- Tag devices appropriately for granular control
- Include comments explaining complex access rules
- Test ACL policies before production deployment
Code Style
- HuJSON: Use human-readable formatting with comments
- YAML: 2-space indentation, no tabs
- Markdown: Use consistent heading structure
- JSON: Pretty-print with 2-space indentation
Security Considerations
- Never commit API keys or secrets to the repository
- Use GitHub secrets for sensitive Tailscale credentials
- Regularly audit and review access control policies
- Document security assumptions and threat model
Development Workflow
- Create feature branch for ACL changes
- Make changes to policy.hujson
- Test changes locally if possible
- Create pull request with detailed description
- Review and approve before merging to main
- Monitor GitHub Actions deployment
Testing
- Use Tailscale's built-in ACL test functionality
- Include test cases in the policy file
- Verify connectivity after ACL deployments
- Test edge cases and error scenarios
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.
- 1mo ago First seen · 58 lines · 460 tokens per session scan A 855c88563445
cursorrules is a cursor rule published in the GitHub repository enuno/tailscale-acl (5 stars, last pushed 11mo ago), licensed Apache-2.0. It adds 460 tokens to every session, about $0.0018 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to tailscale-acl, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
index
This repository manages a Kubernetes homelab using GitOps principles with Flux, Talos, and Taskfile-driven workflows.
ci-cd
CI/CD pipeline patterns and deployment rules.
deploy-arch-maintenance
A set of rules for keeping deployment and infrastructure documentation current. Deployment means putting software on servers or other systems so people can use it.
turborepo
Turborepo: monorepo structure, caching, task pipelines.
ci-cd
CI/CD: pipelines, deployment, automation.
pipeline
Full CI pipeline — typecheck, lint, build, test, security, report.