Tutti is a real-time collaboration space where people can work alongside multiple AI agents, including by sharing rooms, editing together, and borrowing agents. It is intended for users who want human-agent or multi-agent collaboration across devices, with open-source and VM versions available. The catalogue entries provide skills and instructions for working with Tutti.
Borrowing it
Nothing to install: this file belongs to tutti-os/tutti. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tutti-os/tutti/main/.codex/skills/tutti-record-agent-session-replay/SKILL.mdgit clone --depth 1 https://github.com/tutti-os/tuttiWrote 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/tutti-os/tutti/tutti-record-agent-session-replay)<a href="https://agentmods.dev/skills/tutti-os/tutti/tutti-record-agent-session-replay"><img src="https://agentmods.dev/badge/skills/tutti-os/tutti/tutti-record-agent-session-replay/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tutti-os/tutti/tutti-record-agent-session-replay"><img src="https://agentmods.dev/badge/skills/tutti-os/tutti/tutti-record-agent-session-replay.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 120 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.1 | $0.00127 | $0.03468 |
| Opus 5 | $0.00063 | $0.01734 |
| Sonnet 5 | $0.00025 | $0.00694 |
| Haiku 4.5 | $0.00013 | $0.00347 |
Grade A, and why
tutti-record-agent-session-replay 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 11d 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 — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Qualify Tutti Agent Session Replay Cassettes
Work from the Tutti checkout. Keep product implementation and the generic
runner in Tutti; keep Case metadata, scenario scripts, fixtures, qualified
Cassettes, and evidence in the external case repository (tutti-os/tutti-replay).
Mental model (script-first, not UI recording):
- Humans/agents write a deterministic
scenarios/*.mjs(prepare / drive / assert) in the case repository — that script is the recording plan. - Record means: Tutti runner launches Desktop, CDP-executes that script against a live Provider, and captures the Cassette. There is no separate click-to-record UI workflow for Session Replay.
- Day-to-day Record/Replay is usually triggered from the case repository QA console; this skill is for Tutti-side CLI qualification, diagnosis, runner or Replay product defects, and new Provider capture support.
Prove qualification in this order:
existing scenario script -> live Record (script + Provider) -> structural audit -> fresh Replay -> optional publication
Never call a Cassette qualified until Record, audit, and a fresh isolated
Replay have all passed. If the scenario script itself is missing or wrong,
stop and use the case repository write-replay-case skill — do not invent
Cases inside Tutti.
Qualification is assertion-specific, not command-specific. A replay passed
exit proves transport and semantic playback, but does not prove that every
Case action ran during Replay. Build a four-column matrix for each core
assertion: Record proof | Cassette proof | Replay proof | Evidence. Stop and
repair the scenario when any required Replay cell is empty.
Start the QA console (case repository)
Browsing Cases, Test Plans, and one-click Record/Replay (which run the same
scenario scripts) live in the case repository (sibling checkout, commonly
../tutti-replay; GitHub: tutti-os/tutti-replay).
From the case repository root:
pnpm install
pnpm dev
Open only http://127.0.0.1:3333 (never the API port :3334). In the UI,
set the Tutti checkout absolute path, create a Test Plan, then Record or
Replay. First-time machine setup: that repository's SETUP.md. Authoring or
mirroring scenario scripts: .agents/skills/write-replay-case/.
What ships with it
2 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.
- 11d ago First seen · 343 lines · 127 tokens per session scan A 552876dc374f
tutti-record-agent-session-replay is a skill published in the GitHub repository tutti-os/tutti (3,707 stars, last pushed 6d ago), licensed Apache-2.0. It adds 127 tokens to every session and 3,468 once invoked, about $0.0006 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-30.
Other skills, from other repositories
browser-testing-with-screenshots
Use when testing web applications with visual verification - automates Chrome browser interactions, element selection, and screenshot capture for confirming UI functionality.
test-automation
Execute Vitest and Playwright test suites with result collection and failure analysis.
qa-testing
Generate and execute API and E2E tests with quality gate assessment.
run-dashboard-e2e-local-changes
Run Playwright E2E (tests/e2e/) against the docker/ all-in-one harness so it reflects LOCAL code changes, not a stale cached image.
rn-testing
This skill should be used when the user asks to "write a Maestro test", "create E2E flows", "add testIDs", "run UI tests", "run E2E tests", "verify a feature works", "test my screen", "set up maestro-runner", "mock network requests", "inspect store state", "write test assertions", or needs guidance on test timing…
capturing-proof
This skill should be used when the user asks to "capture proof", "record a demo of this feature", "make a video showing it works", "record the flow for the PR", "generate a PR body", "capture screenshots for the PR", "proof-capture", or when a verified feature needs PR-ready proof artifacts (video + numbered…