welcome

welcome is a skill for Claude Code, Codex from taslim/nanoclaw-gws-ea. It costs 33 tokens per session (985 once invoked), scanned A, a copy of welcome, MIT.

A greeting and onboarding routine for a newly connected communication channel. It introduces the agent, gives a brief overview, and offers either exploration or immediate help.

In plain words
What is it for?
Use it when a channel is first connected to welcome the user, explain what the agent can do, and guide them into a first task or capability demonstration.
Why use it?
It provides a consistent first interaction without overwhelming a new user with a complete capability list. It also reveals additional capabilities one at a time when requested.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md.

Good fit Use it when a channel is first connected to welcome the user, explain what the agent can do, and guide them into a first task or capability demonstration.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/taslim/nanoclaw-gws-ea/welcome
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 taslim/nanoclaw-gws-ea --skill welcome
Clone the repo
git clone --depth 1 https://github.com/taslim/nanoclaw-gws-ea

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 welcome

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/taslim/nanoclaw-gws-ea/welcome"><img src="https://agentmods.dev/badge/skills/taslim/nanoclaw-gws-ea/welcome.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 985 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.00985
Opus 5.5 $0.00013 $0.00394
Sonnet 5.5 $0.00007 $0.00197
Haiku 4.5 $0.00003 $0.00098

Measured 1mo ago against content hash d650078874f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

welcome 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 1mo 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

91% identical to welcome — 32 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.

container/skills/welcome/SKILL.md · 85 lines

How it starts

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

/welcome — Channel Onboarding (Updated)

You've just been connected to a new user. This your time to shine and make a strong first impression. Introduce yourself and guide the user through what you can do. you got this!

What to do

  1. Send a short, warm greeting
  2. State your name (from your system prompt / CLAUDE.md)
  3. Signal that you're capable of a lot — but don't list everything upfront. Be intriguing, not encyclopedic
  4. Ask: would they like to explore what you can do, or jump straight into something?

If they want to explore: drip-feed one capability at a time. Briefly explain it, offer to demo a compelling example or let them try it. Never dump a full list.

If they want to jump in: just go.


Capabilities to reveal (in order)

Reveal these one at a time, in this sequence. Each should be 2–4 sentences max.

1. Memory & Context Over Time

You remember things across conversations — projects, preferences, people, decisions. Users don't have to re-explain context every session. The more they work with you, the more situationally aware you become.

2. Spawning Persistent Agents (create_agent)

You can spin up other named agents — a Researcher, a Builder, a Calendar agent — each with their own memory, workspace, and personality. They're addressable destinations: you delegate, they work, they report back. These aren't one-shot tasks; they accumulate context across sessions.

3. Scheduled & Background Tasks

You can run tasks on a schedule — daily briefings, monitors that alert only when something matters, recurring reminders. For bigger jobs, you can spin up an agent that works in the background while the conversation continues.

4. Research & Web Browsing

You can browse the web like a person — read articles, pull live data, summarize reports, compare products, answer questions that aren't in your training data. Ask me "what's the latest on X" or "find the best Y for Z" and I'll actually look it up. Very powerful when combined with scheduled tasks.

Read the full file on GitHub · 85 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. 1mo ago First seen · 85 lines · 33 tokens per session scan A d650078874f0

Subscribe to this mod's changes

welcome is a skill published in the GitHub repository taslim/nanoclaw-gws-ea (11 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 985 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to welcome, differing in 32 lines, and is treated as a copy.

Related

Other skills, from other repositories

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

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

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 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

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…

vercel/next.js · 83 tokens