tailscale-mcp: Instructions file for Codex

AGENTS.md

tailscale-mcp AGENTS.md is an instructions file for Codex, OpenCode from HexSleeves/tailscale-mcp. It costs 649 tokens per session, scanned A, original, MIT.

A set of project instructions that tells an AI coding agent which specialised workflows to use for tasks such as planning, debugging, testing, design review, and code review.

In plain words
What is it for?
Use it to route requests to the right workflow, such as investigating a bug, creating a product plan, reviewing code, checking a website, or assessing developer onboarding.
Why use it?
It reduces guesswork about how the agent should respond to different kinds of requests and helps it follow the project’s configured tools and processes.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Codex; built for gstack.

This is HexSleeves/tailscale-mcp's own configuration. It tells Codex and OpenCode how to work on tailscale-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything tailscale-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to HexSleeves/tailscale-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/HexSleeves/tailscale-mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/HexSleeves/tailscale-mcp

Made for: Codex, OpenCode.

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 tailscale-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/hexsleeves/tailscale-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/hexsleeves/tailscale-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/hexsleeves/tailscale-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/hexsleeves/tailscale-mcp/agents-md/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 tailscale-mcp AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/hexsleeves/tailscale-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/hexsleeves/tailscale-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 649 This file is loaded in full into every session.
When invoked 649 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00649 $0.00649
Opus 5.5 $0.00260 $0.00260
Sonnet 5.5 $0.00130 $0.00130
Haiku 4.5 $0.00065 $0.00065

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

Security

Grade A, and why

tailscale-mcp 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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 50 lines

How it starts

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

Skill routing

When the user's request matches an available skill, invoke it via the Skill tool. The skill has multi-step workflows, checklists, and quality gates that produce better results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is cheaper than a false negative.

Key routing rules:

  • Product ideas, "is this worth building", brainstorming → invoke /office-hours
  • Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
  • Architecture, "does this design make sense" → invoke /plan-eng-review
  • Design system, brand, "how should this look" → invoke /design-consultation
  • Design review of a plan → invoke /plan-design-review
  • Developer experience of a plan → invoke /plan-devex-review
  • "Review everything", full review pipeline → invoke /autoplan
  • Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
  • Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
  • Code review, check the diff, "look at my changes" → invoke /review
  • Visual polish, design audit, "this looks off" → invoke /design-review
  • Developer experience audit, try onboarding → invoke /devex-review
  • Ship, deploy, create a PR, "send it" → invoke /ship
  • Merge + deploy + verify → invoke /land-and-deploy
  • Configure deployment → invoke /setup-deploy
  • Post-deploy monitoring → invoke /canary
  • Update docs after shipping → invoke /document-release
  • Weekly retro, "how'd we do" → invoke /retro
  • Second opinion, codex review → invoke /codex
  • Safety mode, careful mode, lock it down → invoke /careful or /guard
  • Restrict edits to a directory → invoke /freeze or /unfreeze
  • Upgrade gstack → invoke /gstack-upgrade
  • Save progress, "save my work" → invoke /context-save
  • Resume, restore, "where was I" → invoke /context-restore
  • Security audit, OWASP, "is this secure" → invoke /cso
  • Make a PDF, document, publication → invoke /make-pdf
  • Launch real browser for QA → invoke /open-gstack-browser
  • Import cookies for authenticated testing → invoke /setup-browser-cookies
  • Performance regression, page speed, benchmarks → invoke /benchmark
  • Review what gstack has learned → invoke /learn
  • Tune question sensitivity → invoke /plan-tune
  • Code quality dashboard → invoke /health

Read the full file on GitHub · 50 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. 1mo ago First seen · 50 lines · 649 tokens per session scan A 4862fad1f9e5

Subscribe to this mod's changes

tailscale-mcp AGENTS.md is an instructions file published in the GitHub repository HexSleeves/tailscale-mcp (145 stars, last pushed yesterday), licensed MIT. It adds 649 tokens to every session, about $0.0026 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-08-30.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,581 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens