nanoclaw-fleet: Skill for Claude Code

.claude/skills/manage-mounts/SKILL.md

manage-mounts is a skill for Claude Code from thmtz/nanoclaw-fleet. It costs 47 tokens per session (365 once invoked), scanned A, a copy of manage-mounts, MIT.

A tool for controlling which host folders NanoClaw’s agent containers may access. It manages an allowlist and can make access read-only for agents other than the main one.

In plain words
What is it for?
Use it to view, add, remove, or reset container mount permissions, then restart the service so changes take effect.
Why use it?
It limits file access to approved directories and makes the access rules visible and changeable.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is thmtz/nanoclaw-fleet's own configuration. It tells Claude Code how to work on nanoclaw-fleet 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 nanoclaw-fleet configures →

Reuse

Borrowing it

Nothing to install: this file belongs to thmtz/nanoclaw-fleet. 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/thmtz/nanoclaw-fleet/main/.claude/skills/manage-mounts/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/thmtz/nanoclaw-fleet

Made for: Claude Code.

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 manage-mounts

README.md
[![agentmods](https://agentmods.dev/badge/skills/thmtz/nanoclaw-fleet/manage-mounts/github.svg)](https://agentmods.dev/skills/thmtz/nanoclaw-fleet/manage-mounts)
Your own site
<a href="https://agentmods.dev/skills/thmtz/nanoclaw-fleet/manage-mounts"><img src="https://agentmods.dev/badge/skills/thmtz/nanoclaw-fleet/manage-mounts/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 manage-mounts

Your own site · 80×15
<a href="https://agentmods.dev/skills/thmtz/nanoclaw-fleet/manage-mounts"><img src="https://agentmods.dev/badge/skills/thmtz/nanoclaw-fleet/manage-mounts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 365 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 89% copy Near-identical to another mod 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.00047 $0.00365
Opus 5 $0.00023 $0.00182
Sonnet 5 $0.00009 $0.00073
Haiku 4.5 $0.00005 $0.00036

Measured 10d ago against content hash 73318b453470, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

manage-mounts 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 10d 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

This is a copy

89% identical to manage-mounts — 11 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.

.claude/skills/manage-mounts/SKILL.md · 48 lines

What it actually says

Manage Mounts

Configure which host directories NanoClaw agent containers can access. The mount allowlist lives at ~/.config/nanoclaw/mount-allowlist.json.

Show Current Config

cat ~/.config/nanoclaw/mount-allowlist.json 2>/dev/null || echo "No mount allowlist configured"

Show the current config to the user in a readable format: which directories are allowed, whether non-main agents are read-only.

Add Directories

Ask which directories the user wants agents to access. For each path:

  • Validate the path exists
  • Ask if it should be read-only for non-main agents (default: yes)

Build the JSON config and write it:

npx tsx setup/index.ts --step mounts --force -- --json '{"allowedRoots":[{"path":"/path/to/dir","readOnly":false}],"blockedPatterns":[],"nonMainReadOnly":true}'

Use --force to overwrite the existing config.

Remove Directories

Read the current config, show it, ask which entry to remove, write the updated config.

Reset to Empty

npx tsx setup/index.ts --step mounts --force -- --empty

After Changes

Restart the service so containers pick up the new config:

  • macOS: launchctl kickstart -k gui/$(id -u)/com.nanoclaw
  • Linux: systemctl --user restart nanoclaw
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. 10d ago First seen · 48 lines · 47 tokens per session scan A 73318b453470

Subscribe to this mod's changes

manage-mounts is a skill published in the GitHub repository thmtz/nanoclaw-fleet (5 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 365 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to manage-mounts, differing in 11 lines, and is treated as a copy.

Related

Other skills, from other repositories

deploy-docker-compose

Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…

omnigent-ai/omnigent · 84 tokens

compute-env-setup

Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.

companion-inc/feynman · 45 tokens

securing-kubernetes-on-cloud

This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…

xalgorix/xalgorix · 80 tokens

detecting-privilege-escalation-in-kubernetes-pods

Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.

xalgorix/xalgorix · 40 tokens

implementing-rbac-hardening-for-kubernetes

Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.

xalgorix/xalgorix · 41 tokens

docker-socket-mount

Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.

PurpleAILAB/Decepticon · 67 tokens