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 skills add thmtz/nanoclaw-fleet --skill statusgit clone --depth 1 https://github.com/thmtz/nanoclaw-fleetWrote 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/thmtz/nanoclaw-fleet/status)<a href="https://agentmods.dev/skills/thmtz/nanoclaw-fleet/status"><img src="https://agentmods.dev/badge/skills/thmtz/nanoclaw-fleet/status.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.1 | $0.00064 | $0.00414 |
| Opus 5 | $0.00032 | $0.00207 |
| Sonnet 5 | $0.00013 | $0.00083 |
| Haiku 4.5 | $0.00006 | $0.00041 |
Grade A, and why
status 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 7d 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.
What it actually says
/status — fleet dashboard
When to use
The user wants a snapshot of fleet state — master plus every worker, their backends, and uptime. Trigger on any phrasing that maps to "show me what's running":
/statusstatus?fleet statuswhat's running?list workerswho's up?
What to do
Call the mcp__nanoclaw__list_workers MCP tool. The host runs the query synchronously and posts a formatted dashboard (master state + per-worker bullets + summary footer) to the master's channel as a chat message. The dashboard delivery itself counts as your reply — the host drops your trailing turn-text automatically. Just end the turn after the tool call; nothing else to do.
That's the entire skill.
What NOT to do
- Don't try to enumerate workers from
docker psor your own context —list_workersis the only source of truth. It also includes archived workers and master state whichdocker psdoesn't. - Don't paraphrase the dashboard. The format is intentional: the user reads it on a phone, scanning for icons + uptimes. Reformatting loses information.
- Don't run after every message. Only on explicit "show me status" intent.
v1 parity note
This is the v2 equivalent of v1 fleet's /status skill (FORK-SPEC §13.3), which ran tools/nc-status.sh and forwarded the output. The v2 form is simpler because the dashboard logic lives in list_workers itself rather than a separate shell script — the skill just routes the request.
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.
- 7d ago First seen · 34 lines · 64 tokens per session scan A 3cc4e32c9180
status is a skill published in the GitHub repository thmtz/nanoclaw-fleet (5 stars, last pushed 4mo ago), licensed MIT. It adds 64 tokens to every session and 414 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…