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/junmystery/agent-guidance-python/nanoclaw-replnpx skills add JunMystery/Agent-Guidance-Python --skill nanoclaw-replgit clone --depth 1 https://github.com/JunMystery/Agent-Guidance-PythonWrote 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/junmystery/agent-guidance-python/nanoclaw-repl)<a href="https://agentmods.dev/skills/junmystery/agent-guidance-python/nanoclaw-repl"><img src="https://agentmods.dev/badge/skills/junmystery/agent-guidance-python/nanoclaw-repl.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.00031 | $0.00189 |
| Opus 5 | $0.00015 | $0.00095 |
| Sonnet 5 | $0.00006 | $0.00038 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
nanoclaw-repl 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 yesterday.
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.
This is a copy
91% identical to nanoclaw-repl — 9 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.
What it actually says
NanoClaw REPL
Use this skill when running or extending scripts/claw.js.
Capabilities
- persistent markdown-backed sessions
- model switching with
/model - dynamic skill loading with
/load - session branching with
/branch - cross-session search with
/search - history compaction with
/compact - export to md/json/txt with
/export - session metrics with
/metrics
Operating Guidance
- Keep sessions task-focused.
- Branch before high-risk changes.
- Compact after major milestones.
- Export before sharing or archival.
Extension Rules
- keep zero external runtime dependencies
- preserve markdown-as-database compatibility
- keep command handlers deterministic and local
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.
- yesterday First seen · 34 lines · 31 tokens per session scan A a917d56baef8
nanoclaw-repl is a skill published in the GitHub repository JunMystery/Agent-Guidance-Python (2 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 189 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to nanoclaw-repl, differing in 9 lines, and is treated as a copy.
Other skills, from other repositories
voicemode
Voice interaction for Claude Code. Use when users mention voice mode, speak, talk, converse, voice status, or voice troubleshooting.
specimen-authoring
Workflow and hard-won TD patterns for authoring Embody Specimens (the transparent TDXN gallery networks). Load before building or persisting a Specimen.
externalize-operator
MUST READ before calling externalizeop or saveexternalization. Required workflow steps.
multi-instance
Workflow for running multiple TD instances with Envoy, switching between them, and understanding the instance registry.
coding-flow
Light coding workflow: features, fixes, refactors, unit tests, etc.; scales small to large.
debug-operator
TRIGGER when operator errors appear or user reports broken behavior. Systematic diagnosis workflow.