update-setup

update-setup is a skill for Claude Code, Codex from HKUDS/nanobot. It costs 15 tokens per session (1,298 once invoked), scanned A, original, MIT.

A one-time setup wizard for creating a personalised upgrade skill in a nanobot agent workspace. It checks whether an upgrade skill already exists and gathers version and installation details.

In plain words
What is it for?
Preparing nanobot's upgrade instructions and identifying how nanobot is currently installed.
Why use it?
It guides the setup process and helps avoid overwriting an existing upgrade skill without confirmation.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Preparing nanobot's upgrade instructions and identifying how nanobot is currently installed.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hkuds/nanobot/update-setup
About the project

nanobot is a small, self-hosted personal AI agent framework written in Python, providing an agent runtime that can operate through a WebUI, terminal, or chat applications. Users use it to connect language models with tools, memory, MCP integrations, scheduled automation, and multi-agent workflows. The catalogue add-ons provide skills and instructions for working with nanobot.

HKUDS/nanobot · 49,064 stars · on GitHub · nanobot.wiki

Install

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.

Any agent
npx skills add HKUDS/nanobot --skill update-setup
Clone the repo
git clone --depth 1 https://github.com/HKUDS/nanobot

Made for: Claude Code, Codex.

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 update-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/hkuds/nanobot/update-setup/github.svg)](https://agentmods.dev/skills/hkuds/nanobot/update-setup)
Your own site
<a href="https://agentmods.dev/skills/hkuds/nanobot/update-setup"><img src="https://agentmods.dev/badge/skills/hkuds/nanobot/update-setup/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 update-setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/hkuds/nanobot/update-setup"><img src="https://agentmods.dev/badge/skills/hkuds/nanobot/update-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,298 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. Third-party audits
  • Snyk pass 7 Sept 2026
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 4 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Agent Snooping · line 10
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
  • medium Agent Snooping · line 17
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
  • medium Agent Snooping · line 40
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
  • medium Agent Snooping · line 109
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
How audits are shown
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.00015 $0.01298
Opus 5.5 $0.00006 $0.00519
Sonnet 5.5 $0.00003 $0.00260
Haiku 4.5 $0.00002 $0.00130

Measured today against content hash 6c54d421b5b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

update-setup 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

nanobot/skills/update-setup/SKILL.md · 130 lines

How it starts

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

Update Setup

Generate a personalized upgrade skill in Nanobot's agent workspace.

Use the absolute <agent-workspace>/skills/update/SKILL.md path, where <agent-workspace> is shown in the system prompt. Never substitute a project-relative path. If the write is rejected, ask the user to select the agent workspace or enable Full Access before rerunning setup.

Step 1: Check Existing

Use read_file to check if <agent-workspace>/skills/update/SKILL.md already exists.

If it exists, ask the user: "An upgrade skill already exists. Reconfigure?" Wait for the user's reply. If no, stop here.

Step 2: Current Version and Install Clues

Use exec to run nanobot --version. Tell the user the current version.

Then collect install clues with exec. These commands are best-effort; if one fails, keep going and show the useful output:

command -v nanobot || true
python -m pip show nanobot-ai || true
pipx list | sed -n '/nanobot-ai/,+3p' || true
uv tool list | sed -n '/nanobot-ai/,+3p' || true

Summarize what you found in one short paragraph. Use the clues only to suggest a likely install method. Do not treat them as confirmation.

Step 3: Confirm Required Inputs

CRITICAL: Do not write <agent-workspace>/skills/update/SKILL.md until the install method is explicitly confirmed by the user. The install method must come from a user answer or confirmation, not from inference alone. If you cannot get a clear answer, stop and ask the user to rerun this setup when they know how nanobot was installed.

Ask the user the questions below, one at a time, in your response text. Wait for the user's reply before proceeding to the next question. If you cannot get a clear answer, stop without writing the skill.

Question 1 — Install method:

question: "I found these install clues: <SUMMARY>. Which update method should this workspace use?"
options: ["uv", "pipx", "pip", "source (git clone)", "not sure"]

If the user selected not sure, explain the difference between the options and stop. Do not generate the upgrade skill.

Read the full file on GitHub · 130 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. today Changed · -15 tokens per session 6c54d421b5b8
  2. 1mo ago First seen · 130 lines · 30 tokens per session scan A 6bd9b1f642e8

Subscribe to this mod's changes

update-setup is a skill published in the GitHub repository HKUDS/nanobot (49,064 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 1,298 once invoked, about $0.0001 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.