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/shinystar307/nano---openclaw/capabilitiesnpx skills add ShinyStar307/nano---Openclaw --skill capabilitiesgit clone --depth 1 https://github.com/ShinyStar307/nano---OpenclawWrote 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/shinystar307/nano---openclaw/capabilities)<a href="https://agentmods.dev/skills/shinystar307/nano---openclaw/capabilities"><img src="https://agentmods.dev/badge/skills/shinystar307/nano---openclaw/capabilities.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.00046 | $0.00825 |
| Opus 5 | $0.00023 | $0.00413 |
| Sonnet 5 | $0.00009 | $0.00165 |
| Haiku 4.5 | $0.00005 | $0.00082 |
Grade B, and why
capabilities 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 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls -1 /home/node/.claude/skills/ 2>/dev/null || echo "No skills found" This is a copy
100% identical to capabilities — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/capabilities — System Capabilities Report
Generate a structured read-only report of what this NanoClaw instance can do.
Main-channel check: Only the main channel has /workspace/project mounted. Run:
test -d /workspace/project && echo "MAIN" || echo "NOT_MAIN"
If NOT_MAIN, respond with:
This command is available in your main chat only. Send
/capabilitiesthere to see what I can do.
Then stop — do not generate the report.
How to gather the information
Run these commands and compile the results into the report format below.
1. Installed skills
List skill directories available to you:
ls -1 /home/node/.claude/skills/ 2>/dev/null || echo "No skills found"
Each directory is an installed skill. The directory name is the skill name (e.g., agent-browser → /agent-browser).
2. Available tools
Read the allowed tools from your SDK configuration. You always have access to:
- Core: Bash, Read, Write, Edit, Glob, Grep
- Web: WebSearch, WebFetch
- Orchestration: Task, TaskOutput, TaskStop, TeamCreate, TeamDelete, SendMessage
- Other: TodoWrite, ToolSearch, Skill, NotebookEdit
- MCP: mcp__nanoclaw__* (messaging, tasks, group management)
3. MCP server tools
The NanoClaw MCP server exposes these tools (via mcp__nanoclaw__* prefix):
send_message— send a message to the user/groupschedule_task— schedule a recurring or one-time tasklist_tasks— list scheduled taskspause_task— pause a scheduled taskresume_task— resume a paused taskcancel_task— cancel and delete a taskupdate_task— update an existing taskregister_group— register a new chat/group (main only)
4. Container skills (Bash tools)
Check for executable tools in the container:
which agent-browser 2>/dev/null && echo "agent-browser: available" || echo "agent-browser: not found"
5. Group info
ls /workspace/group/CLAUDE.md 2>/dev/null && echo "Group memory: yes" || echo "Group memory: no"
ls /workspace/extra/ 2>/dev/null && echo "Extra mounts: $(ls /workspace/extra/ 2>/dev/null | wc -l | tr -d ' ')" || echo "Extra mounts: none"
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 · 101 lines · 46 tokens per session scan B 330cd8c041f3
capabilities is a skill published in the GitHub repository ShinyStar307/nano---Openclaw (5 stars, last pushed 5mo ago), licensed MIT. It adds 46 tokens to every session and 825 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). It is 100% identical to capabilities, differing in 0 lines, and is treated as a copy.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…