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/szsip239/teamclaw/agent-initnpx skills add szsip239/teamclaw --skill agent-initgit clone --depth 1 https://github.com/szsip239/teamclawWrote 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/szsip239/teamclaw/agent-init)<a href="https://agentmods.dev/skills/szsip239/teamclaw/agent-init"><img src="https://agentmods.dev/badge/skills/szsip239/teamclaw/agent-init.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.00108 | $0.01551 |
| Opus 5 | $0.00054 | $0.00776 |
| Sonnet 5 | $0.00022 | $0.00310 |
| Haiku 4.5 | $0.00011 | $0.00155 |
Grade C, and why
agent-init scanned grade C with 2 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 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- If uv missing: `curl -LsSf https://astral.sh/uv/install.sh | sh` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- If uv missing: `curl -LsSf https://astral.sh/uv/install.sh | sh` How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Init
Initialize OpenClaw agent workspace with tailored MD files through an interactive interview.
Workflow
Phase 1: Interview (MANDATORY — do not skip)
Before generating ANY files, gather context through conversation. Ask in batches of 2-3 questions:
Batch 1 — Identity & Purpose:
- What is this agent's primary purpose? (e.g., coding assistant, research, DevOps, personal assistant)
- What name and emoji? Any personality traits?
Batch 2 — User Profile:
- Who will use this agent? (name, timezone, preferences)
- Communication style preference? (formal/casual, verbose/terse, language)
Batch 3 — Environment:
- Is this a container instance or external instance?
- What tools/languages does the agent need? (Python, Node, etc.)
- Any specific workflows or periodic tasks?
Batch 4 — Boundaries:
- Any topics or actions the agent should avoid?
- Privacy requirements beyond defaults?
Only proceed to Phase 2 after user confirms the interview is complete.
Phase 2: Environment Check
Run scripts/check-env.sh to detect Python/uv status:
bash <skill-path>/scripts/check-env.sh
If uv is missing and user wants Python support:
bash <skill-path>/scripts/check-env.sh --install
For container instances, run inside the container:
docker exec <containerId> bash -c "which uv && uv --version || echo 'uv: NOT FOUND'"
Phase 3: Generate Files
Generate files in this order, showing each to user for confirmation before writing:
- IDENTITY.md — Fill in fields from interview
- USER.md — Fill in user profile
- SOUL.md — Rewrite content, keep 4-section structure (Core Truths / Boundaries / Vibe / Continuity)
- TOOLS.md — Add environment info, Python/uv config, documentation access notes
- AGENTS.md — Extend default template with domain-specific sections (see strategy below)
- HEARTBEAT.md — Add periodic tasks if any
- BOOTSTRAP.md — Skip unless user wants first-run ritual
AGENTS.md Strategy: Extend, Don't Replace
What ships with it
3 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.
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 · 167 lines · 108 tokens per session scan C 28bcead46dfb
agent-init is a skill published in the GitHub repository szsip239/teamclaw (112 stars, last pushed 18d ago), licensed MIT. It adds 108 tokens to every session and 1,551 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, 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
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…
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…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…