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/sonichi/sutando/self-upgradenpx skills add sonichi/sutando --skill self-upgradegit clone --depth 1 https://github.com/sonichi/sutandoWrote 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/sonichi/sutando/self-upgrade)<a href="https://agentmods.dev/skills/sonichi/sutando/self-upgrade"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/self-upgrade.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01051 |
| Opus 5 | $0.00000 | $0.00526 |
| Sonnet 5 | $0.00000 | $0.00210 |
| Haiku 4.5 | $0.00000 | $0.00105 |
Grade A, and why
self-upgrade 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 5d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Self-upgrade
Safely upgrade this Sutando checkout to the latest upstream code without bricking the running core session — the "success path" distilled from a real 2026-07-20 upgrade that would otherwise hang (and did, the first time).
Usage: /self-upgrade
Why this skill exists
A naive "pull + restart" self-upgrade gets stuck, because:
src/restart.shends withexec bash src/startup.sh.src/startup.shruns foreground work and foreground-parents the credential-proxy (atsxprocess that never exits). The open-source core is headless: the optional Swift helpers (ax-read,Sutando.app) are built separately by the app packaging/setup workflow, not by core startup.- So running
restart.shinline from the core session never returns — the Bash call hangs forever, the task never gets a result, and from the owner's side you've "gone stuck."
The fix is simple once you know it: hand the restart to the same durable tmux
server that owns the core. A plain nohup … & is not enough: the supported
Codex executor tears down that process tree when the tool call ends. A detached
tmux service pane survives that boundary, remains the parent of restarted
services, and lets startup recreate the managed task notifier.
On activation
Step 1 — Pull + durable restart handoff (mechanical)
Run the helper. It aborts safely on a dirty tree or a non-fast-forward, pulls
--ff-only, and launches src/restart.sh in the persistent
sutando-services tmux session:
bash skills/self-upgrade/scripts/upgrade.sh # origin/main
# bash skills/self-upgrade/scripts/upgrade.sh --no-restart # pull only
Exit 0 = upgraded (or already latest); exit 2 = aborted (dirty tree /
not a fast-forward) — surface the reason and stop.
If the diff touched package*.json / tsconfig / *.swift / requirements
(the script prints this), a rebuild may be needed. For *.swift, rebuild the
optional menu-bar app and ax-read through the app setup workflow; core
startup.sh intentionally does not build them. For npm deps run npm ci
before relying on the TS services.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 92 lines · 0 tokens per session scan A 36231bce36cf
self-upgrade is a skill published in the GitHub repository sonichi/sutando (391 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,051 tokens. 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
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.
app-builder
Build and edit small, personal visual tools and artifacts — dashboards, trackers, calculators, data visualizations, charts, simple landing pages, and slide decks the user wants for THEMSELVES. This is the right skill whenever the user asks to "visualize this," "make a chart," or "build an artifact" for their own use…
contacts
Manage contacts, communication channels, access control, and invite links.
assistant-migration
Migrate from ChatGPT, Claude, OpenClaw, Hermes, Manus, and other AI assistants into Vellum by inspecting their data exports, conversation archives, files, prompts, custom instructions, memory, saved memories, tools, GPTs, workflows, integrations, and relationships, then mapping as much as safely possible into Vellum…
guardian-verify-setup
Set up channel verification for phone, Telegram, Slack, Discord, or email channels via outbound verification flow.
schedule
Reminders, automations, and recurring page, dashboard, or status monitoring (cron, RRULE, or fire-at).