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/crypdick/pynchy/docs-managernpx skills add crypdick/pynchy --skill docs-managergit clone --depth 1 https://github.com/crypdick/pynchyWhat 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.00068 | $0.00686 |
| Opus 5 | $0.00034 | $0.00343 |
| Sonnet 5 | $0.00014 | $0.00137 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
Documentation Manager 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Manager
Helps decide where to document things and maintain consistency across Pynchy docs.
Style Guide
- Write for a user trying to achieve a goal. Don't chronicle the evolution of the codebase. Don't go into unnecessary technical details that are not relevant to the user's goal.
- Follow the Google Style Guide. Write in the present tense. Don't use "we" or "they". Write in the active voice. Don't use "is" or "are".
- Read
docs/contributing/contributing-docs.mdfor the full documentation philosophy and information architecture rules.
Where to Document What
Quick decision tree:
New feature?
- Architecture decision →
docs/architecture/(find the relevant topic file, or create a new one) - Installation requirement →
docs/install.md - Security implication →
docs/architecture/security.md - Development workflow change →
.claude/skills/pynchy-dev/SKILL.md
Bug fix?
- If it needs install change →
docs/install.md - Usually: No doc update needed
Refactoring?
- If user-visible → Update relevant docs
- If internal only → No doc update
File Purposes
| File | What Goes There |
|---|---|
README.md |
Philosophy, quick start, high-level overview |
docs/install.md |
Complete installation guide |
docs/architecture/security.md |
Security model, threat analysis |
docs/architecture/index.md |
Architecture overview and links to topic pages |
docs/architecture/*.md |
One topic per file (containers, routing, tasks, etc.) |
.claude/skills/ |
Development context skills for Claude Code agents |
Information Architecture Rules
- Single source of truth — Every concept explained in exactly one place. Cross-link, don't duplicate.
- Tree-shaped navigation — Root files have links + short summaries. Leaf files have the actual content.
- Small, focused files — One topic per file. If it covers multiple concerns, split it.
Validation
Before committing:
# Check for broken links
uv run mkdocs build --strict
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 · 78 lines · 68 tokens per session scan A 27e9370cbb9d
Documentation Manager is a skill published in the GitHub repository crypdick/pynchy (10 stars, last pushed 7d ago), licensed MIT. It adds 68 tokens to every session and 686 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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-telegram
Add Telegram channel integration via Chat SDK.
migrate-slack-agents
Migrate a classic single-bot Slack install to one provisioned Slack app per existing agent group while preserving agent identities, workspaces, memory, and wiring behavior — or record the operator's choice to stay on classic, which remains supported. Use when /update-nanoclaw surfaces the Slack agents requirement, or…
slack-agent-flow
Let an existing Slack agent create new agents that arrive as their own Slack bots — provisioned app, operator DM, and a shared three-way room, hot-started without a host restart.
add-imessage
Add iMessage to NanoClaw — one channel, two backends. Local (this Mac's chat.db via the Chat SDK bridge; macOS + Full Disk Access) or Hosted iMessage (via photon.codes — native spectrum-ts with a device-login wizard; any OS, no Mac relay). Triggers on "add imessage", "connect imessage", "add photon", "imessage via…