An interactive guide for changing NanoClaw or adding new capabilities. It first asks questions about the requested change and then identifies the relevant code and testing steps.

Use it when adding inputs such as Telegram, Slack, or email, modifying message handling, or integrating another service.

It turns a broad customization request into a concrete plan for changing channels, triggers, integrations, routing, or other behavior.

customize — Skill by refactornator

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.

agentmods

npx agentmods add skills/refactornator/nanoflash/customize

Any agent

npx skills add refactornator/nanoflash --skill customize

Clone the repo

git clone --depth 1 https://github.com/refactornator/nanoflash

Made for: Claude Code, Codex.

Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 965 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 88% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5	$0.00060	$0.00965
Opus 5	$0.00030	$0.00483
Sonnet 5	$0.00012	$0.00193
Haiku 4.5	$0.00006	$0.00097

Measured 2d ago against content hash 6fdbd0bf0605, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

customize 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 2d 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.

Origin

This is a copy

88% identical to customize — 18 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.

.claude/skills/customize/SKILL.md · 111 lines

How it starts

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

NanoClaw Customization

This skill helps users add capabilities or modify behavior. Use AskUserQuestion to understand what they want before making changes.

Workflow

Understand the request - Ask clarifying questions
Plan the changes - Identify files to modify. If a skill exists for the request (e.g., /add-telegram for adding Telegram), invoke it instead of implementing manually.
Implement - Make changes directly to the code
Test guidance - Tell user how to verify

Key Files

File	Purpose
`src/index.ts`	Orchestrator: state, message loop, agent invocation
`src/channels/whatsapp.ts`	WhatsApp connection, auth, send/receive
`src/ipc.ts`	IPC watcher and task processing
`src/router.ts`	Message formatting and outbound routing
`src/types.ts`	TypeScript interfaces (includes Channel)
`src/config.ts`	Assistant name, trigger pattern, directories
`src/db.ts`	Database initialization and queries
`src/whatsapp-auth.ts`	Standalone WhatsApp authentication script
`groups/CLAUDE.md`	Global memory/persona

Common Customization Patterns

Adding a New Input Channel (e.g., Telegram, Slack, Email)

Questions to ask:

Which channel? (Telegram, Slack, Discord, email, SMS, etc.)
Same trigger word or different?
Same memory hierarchy or separate?
Should messages from this channel go to existing groups or new ones?

Implementation pattern:

Create src/channels/{name}.ts implementing the Channel interface from src/types.ts (see src/channels/whatsapp.ts for reference)
Add the channel instance to main() in src/index.ts and wire callbacks (onMessage, onChatMetadata)
Messages are stored via the onMessage callback; routing is automatic via ownsJid()

Adding a New MCP Integration

Questions to ask:

What service? (Calendar, Notion, database, etc.)
What operations needed? (read, write, both)
Which groups should have access?

Implementation:

Add MCP server config to the container settings (see src/container-runner.ts for how MCP servers are mounted)
Document available tools in groups/CLAUDE.md

Read the full file on GitHub · 111 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.

2d ago First seen · 111 lines · 60 tokens per session scan A 6fdbd0bf0605

Subscribe to this mod's changes

customize is a skill published in the GitHub repository refactornator/nanoflash (5 stars, last pushed 4mo ago), licensed MIT. It adds 60 tokens to every session and 965 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to customize, differing in 18 lines, and is treated as a copy.

Building agents

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens