NanoClaw is an AI assistant that runs agents inside separate Linux containers, isolating their files and execution environments. People use it to connect agents to messaging services and run assistants with memory and scheduled jobs. The catalogue contains skills and instructions for extending or operating NanoClaw.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/nanocoai/nanoclawnpx agentmods add skills/nanocoai/nanoclaw/add-clidashWrote 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/nanocoai/nanoclaw/add-clidash)<a href="https://agentmods.dev/skills/nanocoai/nanoclaw/add-clidash"><img src="https://agentmods.dev/badge/skills/nanocoai/nanoclaw/add-clidash/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.
<a href="https://agentmods.dev/skills/nanocoai/nanoclaw/add-clidash"><img src="https://agentmods.dev/badge/skills/nanocoai/nanoclaw/add-clidash.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 3 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 48 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 Rogue Agent · line 123 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 127 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00087 | $0.01819 |
| Opus 5 | $0.00044 | $0.00910 |
| Sonnet 5 | $0.00017 | $0.00364 |
| Haiku 4.5 | $0.00009 | $0.00182 |
Grade A, and why
add-clidash scanned grade A 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://127.0.0.1:4690/api/clis | head -c 400 # CLIs + discovered resources How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/add-clidash — CLI-derived read-only dashboard
clidash is a small, read-only web dashboard. You point it at any CLI that can
list resources as JSON (NanoClaw's ncl, docker, kubectl, …) and it builds
the dashboard at runtime: one tab per resource, a generic table over whatever
columns the rows have. A new ncl resource becomes a new tab and a new column
becomes a new table column with zero code changes.
It ships pre-wired for NanoClaw's ncl CLI and adds three NanoClaw-aware
panels driven entirely by config:
- Agents overview — status cards joining groups + sessions + messaging groups + wirings (green <15m / amber <2h / red older).
- Activity — per-session inbound/outbound message totals and a daily series,
read directly from the session DBs (
nclhas no messages resource). - Logs — last N lines of allowlisted host log files.
- Files — a read-only viewer for group skills,
CLAUDE.md, and profiles.
Why it's safe
clidash is read-only by construction: the server can only execFile the
argv templates in its config. {resource} is the sole substitution and is
allowlist-validated against the discovered/static resource set before exec —
never a shell, no free-form input reaches argv. There is no auth; the network
is the auth boundary — it binds 127.0.0.1 by default. Only ever bind a
private interface (e.g. a tailnet IP), never a public one.
It's distinct from /add-dashboard (which pushes JSON snapshots to a separate
@nanoco/nanoclaw-dashboard npm package): clidash has zero dependencies, no
build step, no push pipeline, and no edits to NanoClaw source — it just reads
ncl and the session DBs.
Steps
1. Copy the tool into place
clidash is fully self-contained — copy the whole directory in:
tools/ is not a standard NanoClaw directory and cp -R won't create it, so
make it first:
mkdir -p tools
cp -R .claude/skills/add-clidash/add/tools/clidash tools/clidash
That is the only file change this skill makes. Nothing in NanoClaw src/ is
touched, no dependency is added.
What ships with it
35 files 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.
- add/tools/clidash/activity.js 3.5 KB runs code
- add/tools/clidash/clidash.config.example.json 3.3 KB
- add/tools/clidash/docs.js 3.7 KB runs code
- add/tools/clidash/logs.js 667 B runs code
- add/tools/clidash/package.json 347 B
- add/tools/clidash/parsers.js 3.3 KB runs code
- add/tools/clidash/public/app.js 33 KB runs code
- add/tools/clidash/public/apple-touch-icon.png 5.3 KB
- add/tools/clidash/public/favicon.ico 547 B
- add/tools/clidash/public/favicon.svg 570 B
- add/tools/clidash/public/icon-192.png 6.5 KB
- add/tools/clidash/public/icon-512.png 18 KB
- add/tools/clidash/public/index.html 1.9 KB
- add/tools/clidash/public/md.js 2.7 KB runs code
- add/tools/clidash/public/site.webmanifest 298 B
- add/tools/clidash/public/style.css 18 KB
- add/tools/clidash/README.md 4.0 KB
- add/tools/clidash/server.js 17 KB runs code
- add/tools/clidash/test/activity-server.test.js 2.3 KB runs code
- add/tools/clidash/test/activity.test.js 3.8 KB runs code
- add/tools/clidash/test/cmd.test.js 3.4 KB runs code
- add/tools/clidash/test/css.test.js 991 B runs code
- add/tools/clidash/test/docs-server.test.js 4.0 KB runs code
- add/tools/clidash/test/docs.test.js 4.4 KB runs code
- add/tools/clidash/test/fixtures/ncl-help.txt 4.1 KB
- add/tools/clidash/test/fixtures/stub-cli.js 1.8 KB runs code
- add/tools/clidash/test/help.test.js 2.2 KB runs code
- add/tools/clidash/test/logs.test.js 2.9 KB runs code
- add/tools/clidash/test/md.test.js 2.9 KB runs code
- add/tools/clidash/test/ncl-overview.test.js 3.5 KB runs code
- add/tools/clidash/test/parsers.test.js 4.0 KB runs code
- add/tools/clidash/test/server.test.js 8.9 KB runs code
- add/tools/clidash/test/smoke.sh 747 B runs code
- add/tools/clidash/views/ncl-overview.js 1.9 KB runs code
- REMOVE.md 544 B
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.
- 11d ago First seen · 169 lines · 87 tokens per session scan A 50ddf1cba2eb
add-clidash is a skill published in the GitHub repository nanocoai/nanoclaw (30,736 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 1,819 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
Pynchy Development
Use when running pynchy locally — running the app, tests, linting, formatting, prek hooks, or rebuilding the agent container. Also use when determining whether you're on the live Pynchy host or a local machine, and for debugging agent behavior-- session transcript branching, inspecting message history and agent traces…
Pynchy Plugin Authoring
Use when creating, scaffolding, or updating a pynchy plugin, including channels, MCP servers, skills, agent cores, workspace specs, and container runtime plugins. Also use when users ask how to register plugins via config.toml, add entry points, or validate plugin hook wiring.
slack-token-extractor
Refresh expired Slack browser tokens (xoxc/xoxd) using persistent browser sessions. Use when Slack MCP tools fail with authentication errors.
x-integration
Post tweets, like, reply, retweet, and quote on X (Twitter) using browser automation. Use when the user asks you to interact with X/Twitter.
Documentation Manager
Use when writing or reviewing pynchy documentation, deciding where to document things, updating the docs, checking doc consistency, or fixing broken links. Covers information architecture, writing philosophy, tree-shaped navigation, doc-code coupling, no hard-coded usernames, extensibility framing for pluggable…
python-heredoc
When running multi-line Python code or code with quotes, apostrophes, or f-strings via Bash, always use heredoc syntax instead of python -c to avoid shell quoting issues.