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 agentmods add skills/hkuds/nanobot/update-setupnpx skills add HKUDS/nanobot --skill update-setupgit clone --depth 1 https://github.com/HKUDS/nanobotWhat 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 | $0.00030 | $0.01313 |
| Opus 5 | $0.00015 | $0.00656 |
| Sonnet 5 | $0.00006 | $0.00263 |
| Haiku 4.5 | $0.00003 | $0.00131 |
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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- update-setup — 92% identical, 20 lines differ
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.
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.
- yesterday First seen · 130 lines · 30 tokens per session scan A 6bd9b1f642e8
update-setup is a skill published in the GitHub repository HKUDS/nanobot (47,535 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 1,313 once invoked, about $0.0002 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-30.
Other skills, from other repositories
clip-hand-skill
Expert knowledge for AI video clipping — yt-dlp downloading, whisper transcription, SRT generation, and ffmpeg processing.
twitter-hand-skill
Expert knowledge for AI Twitter/X management — API v2 reference, content strategy, engagement playbook, safety, and performance tracking.
predictor-hand-skill
Expert knowledge for AI forecasting — superforecasting principles, signal taxonomy, confidence calibration, reasoning chains, and accuracy tracking.
researcher-hand-skill
Expert knowledge for AI deep research — methodology, source evaluation, search optimization, cross-referencing, synthesis, and citation formats.
collector-hand-skill
Expert knowledge for AI intelligence collection — OSINT methodology, entity extraction, knowledge graphs, change detection, and sentiment analysis.
lead-hand-skill
Expert knowledge for AI lead generation — web research, enrichment, scoring, deduplication, and report generation.