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 dylantirandaz/tailscale-compute-mcp --skill tailscale-compute-fleetgit clone --depth 1 https://github.com/dylantirandaz/tailscale-compute-mcpWrote 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/dylantirandaz/tailscale-compute-mcp/tailscale-compute-fleet)<a href="https://agentmods.dev/skills/dylantirandaz/tailscale-compute-mcp/tailscale-compute-fleet"><img src="https://agentmods.dev/badge/skills/dylantirandaz/tailscale-compute-mcp/tailscale-compute-fleet/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/dylantirandaz/tailscale-compute-mcp/tailscale-compute-fleet"><img src="https://agentmods.dev/badge/skills/dylantirandaz/tailscale-compute-mcp/tailscale-compute-fleet.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.00029 | $0.01069 |
| Opus 5 | $0.00015 | $0.00535 |
| Sonnet 5 | $0.00006 | $0.00214 |
| Haiku 4.5 | $0.00003 | $0.00107 |
Grade A, and why
tailscale-compute-fleet 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 11d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tailscale Compute Fleet
Use this skill when two or more MCP servers expose Tailscale Compute tools. Each MCP server controls one node. The MCP server does not pool CPU, GPU, or memory. It does not make a command distributed.
Invariants
- Keep one named MCP server for each node.
- An explicit user target overrides each placement rule.
- Refuse a node that does not meet the platform, architecture, memory, accelerator, or toolchain requirements of the command.
- Never replace a requested accelerator with a CPU or another backend.
- Never use a hidden queue. Return a node-busy result or select a different eligible node explicitly.
- Use the distributed runtime that the repository declares. Do not install or infer a runtime only to distribute a command.
- Do not claim that memory or accelerator resources are combined across Macs.
- Keep the control connection on the Tailscale address. Use a Thunderbolt data path only when the project supplies or requests a valid runtime host file.
Independent job placement
- Identify each available MCP server that exposes
compute_statusandcompute_job_start. - Call
compute_statuson each node. Reject unavailable nodes and nodes with incompatible hardware or operating systems. - Call
compute_job_listfor active states when current durable-job load is not available. - Build the task dependency graph. Send only independent tasks to different nodes at the same time.
- Select the eligible node with the lowest active-job count. Then use the lowest reported load. Use the MCP server name as the stable final tie-breaker.
- Start each task with a stable
idempotencyKey, a workflow label, and each requiredartifactPath. - Record the selected MCP server name and returned job ID. Poll, cancel, delete, and fetch through that same server.
- Fetch immutable artifacts by job ID. Check each fetched SHA-256 value against the terminal receipt before a dependent task uses the files.
Do not move an active durable job between nodes. A retry must use the same MCP server and the same request data. This lets idempotency return the first job.
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.
- 11d ago First seen · 102 lines · 29 tokens per session scan A e41bf9114afd
tailscale-compute-fleet is a skill published in the GitHub repository dylantirandaz/tailscale-compute-mcp (1 stars, last pushed 27d ago), licensed MIT. It adds 29 tokens to every session and 1,069 once invoked, about $0.0001 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.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…