nextclaw-autostart

nextclaw-autostart is a skill for Claude Code, Codex from Peiiii/nextclaw. It costs 86 tokens per session (898 once invoked), scanned B, original, MIT.

A guide for making the NextClaw background service start automatically when a computer starts or a user logs in. NextClaw is a command-line program, while a service runs in the background without needing to be started manually.

In plain words
What is it for?
It helps install login or boot startup using the operating system’s service mechanisms, check the current setup, diagnose problems, and uninstall it.
Why use it?
Starting NextClaw once does not normally make it return after a restart. This helps users set up, inspect, diagnose, or remove automatic startup explicitly on macOS, Linux, or Windows.

Skill for Claude CodeCodex

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

Good fit It helps install login or boot startup using the operating system’s service mechanisms, check the current setup, diagnose problems, and uninstall it.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/peiiii/nextclaw/nextclaw-autostart
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 Peiiii/nextclaw --skill nextclaw-autostart
Clone the repo
git clone --depth 1 https://github.com/Peiiii/nextclaw

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 nextclaw-autostart

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/peiiii/nextclaw/nextclaw-autostart"><img src="https://agentmods.dev/badge/skills/peiiii/nextclaw/nextclaw-autostart.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 898 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 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 Privilege Escalation · line 26
    Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
    Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
  • medium Privilege Escalation · line 32
    Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
    Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00086 $0.00898
Opus 5 $0.00043 $0.00449
Sonnet 5 $0.00017 $0.00180
Haiku 4.5 $0.00009 $0.00090

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

Security

Grade B, and why

nextclaw-autostart scanned grade B with 1 finding 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 11d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

- Linux system-level boot autostart: `sudo nextclaw service install-systemd --system`
packages/nextclaw-core/src/features/agent/shared/skills/nextclaw-autostart/SKILL.md · 80 lines

How it starts

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

NextClaw Autostart

This built-in skill helps the AI guide users through NextClaw autostart and reboot recovery without turning service registration into a hidden side effect.

Core Position

  • npm i -g nextclaw installs the CLI only. It should not silently register a host autostart service.
  • nextclaw start starts the current background service. Without host autostart registration, the service usually needs to be started again after an OS reboot.
  • Autostart must be explicit, inspectable, diagnosable, and removable.
  • Prefer a product-level guided setup flow over asking normal users to understand launchd, systemd, or Task Scheduler first.
  • Do not confuse three separate meanings:
    • login/boot autostart,
    • crash supervision,
    • update/restart relaunch.

Existing Commands

  • macOS login autostart: nextclaw service install-launch-agent
  • Linux user-level login autostart: nextclaw service install-systemd --user
  • Linux system-level boot autostart: sudo nextclaw service install-systemd --system
  • Windows login autostart: nextclaw service install-task
  • Status: nextclaw service autostart status
  • Diagnostics: nextclaw service autostart doctor
  • macOS uninstall: nextclaw service uninstall-launch-agent
  • Linux user-level uninstall: nextclaw service uninstall-systemd --user
  • Linux system-level uninstall: sudo nextclaw service uninstall-systemd --system
  • Windows uninstall: nextclaw service uninstall-task

Workflow

  1. Determine whether the user is asking for current behavior, product design, setup help, or troubleshooting.
  2. For current behavior, clearly separate:
    • CLI installation,
    • one-time/background runtime start,
    • host autostart registration.
  3. For setup help:
    • identify the OS,
    • inspect current autostart status,
    • explain what registration will change,
    • ask before performing a mutating registration command,
    • verify with nextclaw service autostart status or doctor,
    • tell the user how to disable it.
  4. For troubleshooting, collect:
    • OS and install method,
    • nextclaw --version,
    • nextclaw status,
    • nextclaw service autostart status,
    • nextclaw service autostart doctor.
  5. Diagnose whether the issue is:
    • autostart not registered,
    • registration failed,
    • executable path changed after update,
    • permission/scope mismatch,
    • port conflict,
    • service starts then crashes.

Read the full file on GitHub · 80 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. 11d ago First seen · 80 lines · 86 tokens per session scan B 07f416018a90

Subscribe to this mod's changes

nextclaw-autostart is a skill published in the GitHub repository Peiiii/nextclaw (256 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 898 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

openclaw-github-dedupe

Investigate a cluster of GitHub issues and PRs, determine canonical candidates, post duplicate/related status, preserve contributor credit, and execute cleanup actions. Supports autonomous mode for provided-link-only closeout, merge/fix follow-through, changelog, and post-merge issue/PR cleanup.

vincentkoc/dotskills · 68 tokens

openclaw-pr-batch-sweep

Select, review, repair, validate, and land batches of up to 20 low-risk OpenClaw contributor pull requests using Vincent's maintainer preferences and bounded sub-agent lanes. Use for "next 20", broad contributor PR sweeps, merge-candidate mining, or continued PR-batch work where drafts, maintainer work, trivial…

vincentkoc/dotskills · 95 tokens

tmux-lane-orchestrator

Manage one tmux agent lane from its matching ops pane, inspect live pane state and Codex logs on cold start, and produce concise manager summaries for OpenClaw and adjacent project work.

vincentkoc/dotskills · 46 tokens

ghcrawl-cluster-operator

Use when inspecting a ghcrawl SQLite store, pulling GitHub issue/PR data, refreshing summaries, embeddings, and clusters, or extracting one cluster and its evidence through the ghcrawl CLI.

vincentkoc/dotskills · 45 tokens

opik-optimizer

Optimize LLM prompts, tools, and agents in Opik using standardized optimizer workflows (prompt optimization, tool optimization, and parameter tuning), dataset/metric wiring, and result interpretation.

vincentkoc/dotskills · 41 tokens

org-branch-cleanup

Audit and safely prune stale branches across a GitHub organization with immutable snapshots, conservative merged-PR classification, live SHA/protection/open-PR revalidation, resumable deletion ledgers, and post-delete verification. Use when a maintainer asks to clean up old, dead, merged, bot-created, or abandoned…

vincentkoc/dotskills · 91 tokens