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/nutthouse/tutti/openclawnpx skills add nutthouse/tutti --skill openclawgit clone --depth 1 https://github.com/nutthouse/tuttiWhat 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.00000 | $0.00645 |
| Opus 5 | $0.00000 | $0.00322 |
| Sonnet 5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
openclaw 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tutti OpenClaw Skill (Starter)
Use this skill to orchestrate a Tutti workspace from another agent loop.
Reference wrapper:
integrations/openclaw/tutti_openclaw.pyintegrations/openclaw/action-contract.json
If your tt binary is older than repo main, invoke the wrapper with:
--tt-bin "cargo run --quiet --"
Trigger
Use when asked to launch/monitor/verify/stop a multi-agent workspace managed by Tutti.
Preconditions
- Run from workspace root (
tutti.tomlpresent). - Run
tt doctorbefore launching long workflows. - Prefer
.tutti/state/*.jsonandtt verify --last --jsonfor verification reads.
Intent Mapping
launch_team:tt uplaunch_agent:tt up <agent>run_workflow:tt run <workflow> [--agent <agent>] [--strict] [--json]list_workflows:tt run --list --jsonplan_workflow:tt run <workflow> --dry-run --jsonverify_team:tt verify [--workflow <name>] [--agent <agent>] [--strict] [--json]generate_handoff:tt handoff generate <agent> --jsonlist_handoffs:tt handoff list --json [--agent <agent>]apply_handoff:tt handoff apply <agent> [--packet <path>]team_status:tt statusagent_output:tt peek <agent> --lines <n>stop_agent:tt down <agent>stop_team:tt downread_verify_status:tt verify --last --json(fallback:.tutti/state/verify-last.json)
Execution Pattern
- Preflight:
python3 integrations/openclaw/tutti_openclaw.py doctor_check- stop if non-zero and report failures.
- Launch:
... launch_teamor... launch_agent <agent>.
- Work:
... list_workflows, then... run_workflow <workflow>.
- Verify:
... verify_team --strictfor gate-style checks.
- Stop:
... stop_teamor... stop_agent <agent>.
Failure Policy
- Non-zero
ttexit: surface command + stderr summary. tt verifynon-strict warnings: report as warning, includett verify --last --jsonfields.- Missing state file: treat as transient for up to 3 short retries.
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 · 71 lines · 0 tokens per session scan A 571b451bffa5
openclaw is a skill published in the GitHub repository nutthouse/tutti (116 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 645 tokens. 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.