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/moltis-org/moltis/claude-codenpx skills add moltis-org/moltis --skill claude-codegit clone --depth 1 https://github.com/moltis-org/moltisWrote 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/moltis-org/moltis/claude-code)<a href="https://agentmods.dev/skills/moltis-org/moltis/claude-code"><img src="https://agentmods.dev/badge/skills/moltis-org/moltis/claude-code.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.00039 | $0.09009 |
| Opus 5 | $0.00019 | $0.04505 |
| Sonnet 5 | $0.00008 | $0.01802 |
| Haiku 4.5 | $0.00004 | $0.00901 |
Grade D, and why
claude-code scanned grade D 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
4. **User:** `~/.claude/settings.json` (global) Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
"deny": ["Read(.env)", "Bash(rm -rf *)"] Copies of this mod
8 near-identical copies found in the catalogue:
- claude-code — 95% identical, 53 lines differ
- claude-code — 94% identical, 27 lines differ
- claude-code — 94% identical, 27 lines differ
- claude-code — 92% identical, 30 lines differ
- claude-code — 92% identical, 30 lines differ
- claude-code — 92% identical, 34 lines differ
- claude-code — 92% identical, 30 lines differ
- claude-code — 92% identical, 34 lines differ
How it starts
The opening of the file, as written. The whole thing — 748 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code — Orchestration Guide
Delegate coding tasks to Claude Code (Anthropic's autonomous coding agent CLI) via the Moltis terminal. Claude Code v2.x can read files, write code, run shell commands, spawn subagents, and manage git workflows autonomously.
Prerequisites
- Install:
npm install -g @anthropic-ai/claude-code - Auth: run
claudeonce to log in (browser OAuth for Pro/Max, or setANTHROPIC_API_KEY) - Console auth:
claude auth login --consolefor API key billing - SSO auth:
claude auth login --ssofor Enterprise - Check status:
claude auth status(JSON) orclaude auth status --text(human-readable) - Health check:
claude doctor— checks auto-updater and installation health - Version check:
claude --version(requires v2.x+) - Update:
claude updateorclaude upgrade
Two Orchestration Modes
Moltis interacts with Claude Code in two fundamentally different ways. Choose based on the task.
Mode 1: Print Mode (-p) — Non-Interactive (PREFERRED for most tasks)
Print mode runs a one-shot task, returns the result, and exits. No PTY needed. No interactive prompts. This is the cleanest integration path.
terminal(command="claude -p 'Add error handling to all API calls in src/' --allowedTools 'Read,Edit' --max-turns 10", workdir="/path/to/project", timeout=120)
When to use print mode:
- One-shot coding tasks (fix a bug, add a feature, refactor)
- CI/CD automation and scripting
- Structured data extraction with
--json-schema - Piped input processing (
cat file | claude -p "analyze this") - Any task where you don't need multi-turn conversation
Print mode skips ALL interactive dialogs — no workspace trust prompt, no permission confirmations. This makes it ideal for automation.
Mode 2: Interactive PTY via tmux — Multi-Turn Sessions
Interactive mode gives you a full conversational REPL where you can send follow-up prompts, use slash commands, and watch Claude work in real time. Requires tmux orchestration.
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.
- 4d ago First seen · 748 lines · 39 tokens per session scan D a54e6439cc87
claude-code is a skill published in the GitHub repository moltis-org/moltis (2,844 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 9,009 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
migrate-from-openclaw
Migrate from OpenClaw to NanoClaw v2. Detects an existing OpenClaw installation, extracts identity, channel credentials, scheduled tasks, and other config, then guides interactive migration. Triggers on "migrate from openclaw", "openclaw migration", "import from openclaw".
add-dial-tool
Give chosen NanoClaw agents a real phone number as a container tool — the dial CLI baked into the agent image plus OneCLI credential injection for api.getdial.ai, scoped per agent, so the agents you pick can send SMS, place AI voice calls, and receive verification codes from inside the sandbox. Independent of the Dial…
add-ollama-tool
Add Ollama MCP server so the container agent can call local models and optionally manage the Ollama model library.
add-signal
Add Signal channel integration via signal-cli device-link. Native adapter — no Chat SDK bridge.
migrate-from-v1
Finish migrating a NanoClaw v1 install into v2. Run after bash migrate-v2.sh completes. Seeds the owner, migrates legacy memory, reconciles container configs, and helps port custom v1 code. Triggers on "migrate from v1", "finish migration", "v1 migration".
migrate-memory
Migrate legacy NanoClaw and Claude-native memory into the shared memory tree and provider-neutral standing instructions. Run after an update reports the shared-memory breaking change, or when a group still has .seed.md, legacy CLAUDE.md/CLAUDE.local.md, Claude auto-memory, or an unindexed imported-agent-memory.md.…