Borrowing it
Nothing to install: this file belongs to PainInTheNic/MCP-TrueNAS. 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/PainInTheNic/MCP-TrueNAS/main/.claude/skills/truenas-update/SKILL.mdgit clone --depth 1 https://github.com/PainInTheNic/MCP-TrueNASWrote 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/paininthenic/mcp-truenas/truenas-update)<a href="https://agentmods.dev/skills/paininthenic/mcp-truenas/truenas-update"><img src="https://agentmods.dev/badge/skills/paininthenic/mcp-truenas/truenas-update/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/paininthenic/mcp-truenas/truenas-update"><img src="https://agentmods.dev/badge/skills/paininthenic/mcp-truenas/truenas-update.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.00066 | $0.02865 |
| Opus 5 | $0.00033 | $0.01432 |
| Sonnet 5 | $0.00013 | $0.00573 |
| Haiku 4.5 | $0.00007 | $0.00286 |
Grade A, and why
truenas-update 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 today.
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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/truenas-update — TrueNAS Update Cycle (OS + Apps)
Runs the full, repeatable update procedure for Nic's TrueNAS SCALE box: check what's
pending, apply app updates, apply the OS update (staged download → ordered VM
shutdown → apply+reboot → verify), and file a Change Management record in Google
Drive for every change made — no change is too minor to document (see
feedback-document-every-change memory).
This skill exists so the procedure is mechanical, not re-derived. Every command shape, tool-param name, and gotcha below was hard-won across real runs (2026-08-13, 2026-09-02) — follow it exactly rather than improvising from first principles.
Arguments passed: $ARGUMENTS
Dispatch on arguments
- No args / "full" / "update" → run the complete cycle below: check, apply apps, apply OS if pending, verify, document.
- "check" / "status" / "dry-run" → Step 1 only. Report what's pending. Make no changes, file no CM doc.
- "apps" / "apps-only" → Step 1 + Step 2 only. Skip the OS update even if one is pending (report it as still pending).
- "os" / "os-only" → Step 1 + Step 3 only (skip app updates even if pending).
Step 1 — Check what's pending
truenas_check_updates (OS: current version, new version if any, reboot_required)
truenas_list_apps (apps: upgrade_available per app)
If both report nothing pending: tell Nic the system is fully current and stop. No CM doc for "nothing happened."
Step 2 — Apply app updates (do this before the OS update — lower risk, isolates failures)
For each app with upgrade_available: true:
truenas_manage_app app=<name> action=upgrade
This runs as a job (TrueNAS auto-snapshots the app first). Poll with
truenas_list_jobs or re-check truenas_get_app app=<name> until state=RUNNING
and upgrade_available=false. A brief DEPLOYING state between STOPPED→RUNNING
is normal — don't report failure on that alone; check again a few seconds later.
File a CM doc for each app updated (template at the bottom of this file) before moving to Step 3.
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.
- today First seen · 245 lines · 66 tokens per session scan A 03fb32005425
truenas-update is a skill published in the GitHub repository PainInTheNic/MCP-TrueNAS (1 stars, last pushed 2d ago), licensed MIT. It adds 66 tokens to every session and 2,865 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-12.
Other skills, from other repositories
cdn-fallback
Put a 3x-ui inbound behind a CDN (WebSocket, gRPC or xhttp through Cloudflare) or share port 443 between several inbounds using Xray fallbacks. Use when REALITY is blocked or unsuitable, when the server IP must stay hidden behind a CDN, when a real domain and certificate are in play, or when several protocols need to…
multi-node
Attach, secure and operate additional 3x-ui panels as nodes of a master panel — probe before saving, choose a TLS trust mode (verify/skip/pin/mTLS), select which inbounds sync, and monitor health and per-node traffic. Use when asked to add a server to a cluster, set up mTLS between panels, work out which node is…
chainstack
Work with the Chainstack MCP server to manage blockchain nodes and projects. Use when deploying nodes, migrating to Chainstack from another RPC provider such as QuickNode or Alchemy, checking platform status, searching Chainstack docs, contacting the Chainstack team, or interacting with the Chainstack platform API via…
publish-release
Releases a new McpOrchestrator version end to end — version bump PR, tag, and the automated deploy to GitHub Releases, NuGet, and the MCP Registry. Use when asked to release, publish, deploy, ship, or bump the version of McpOrchestrator.
cloudflare-management
Manage Cloudflare Workers, KV, R2, DNS, and cache via MCP. Use when the user asks to list zones, edit DNS records, purge cache, inspect Workers, read/write KV, or list R2 buckets on Cloudflare.
acronis
The first real CLI for the Acronis Cyber Protect Cloud platform - every tenant, agent, and usage metric mirrored locally, with cross-tenant rollups no single API call returns. Trigger phrases: acronis backup health across tenants, find offline acronis agents, acronis usage and billing report, which acronis customers…