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-app-release/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-app-release)<a href="https://agentmods.dev/skills/tutti-os/tutti/tutti-app-release"><img src="https://agentmods.dev/badge/skills/tutti-os/tutti/tutti-app-release/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-app-release"><img src="https://agentmods.dev/badge/skills/tutti-os/tutti/tutti-app-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00080 | $0.03643 |
| Opus 5 | $0.00040 | $0.01821 |
| Sonnet 5 | $0.00016 | $0.00729 |
| Haiku 4.5 | $0.00008 | $0.00364 |
Grade A, and why
tutti-app-release 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 — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tutti App Release
Use this skill when an external app repository publishes a remote Tutti workspace app into App Center release metadata.
The external repository calls the reusable workflow from the Tutti/Tutti repository:
uses: tutti-os/tutti/.github/workflows/publish-tutti-app-release.yml@main
That workflow builds one app package, runs @tutti-os/app-release-tools, uploads immutable release files plus mutable latest.json and versions.json, and can optionally merge that app into the shared catalog.json.
Operating Rules
Inspect before acting:
- Read the caller workflow,
tutti.app.json, package script, and recent GitHub Actions runs. - Confirm whether the user wants a new app release, a catalog refresh, or CI debugging. Do not rerun a release just to repair catalog state.
For catalog publication:
- There are three valid modes. Explain them explicitly when helping a user choose.
- Release only:
publish_catalog: false. This uploads a new app version and updatesapps/<appId>/latest.jsonandversions.json; App Center will see it the next timecatalog.jsonis published. - Release and catalog:
publish_catalog: true. This uploads the app release, then immediately merges that release intocatalog.json. - Catalog only:
catalog_only: true. Use this after a release already succeeded when the user forgot to publish catalog, wants to validate first, or wants to refresh catalog without bumping or uploading a new version. - Do not rerun a full app release just to repair catalog state.
- If the app caller workflow exposes
catalog_only, use that. If it does not, use the Tutti catalog workflow directly or add the caller input when the user wants that repo to support catalog-only dispatch.
For versioning:
- Production releases should be workflow-driven. Run the production caller workflow with
release_bump(patch,minor, ormajor); the reusable workflow calculates the next version from the greater of the packaged manifest version and existing release tags, then creates the tag after the S3 release verifies. - The workflow never bumps or commits app manifest versions. Do not add caller-side release PRs or manifest bump commits to work around protected branches.
- Staging releases should leave
release_bumpempty. The workflow usesmanifest.version+<short git sha>from the packaged manifest and does not create a release tag.
What ships with it
1 file 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 · 300 lines · 80 tokens per session scan A 47ae750f3807
tutti-app-release is a skill published in the GitHub repository tutti-os/tutti (3,700 stars, last pushed 5d ago), licensed Apache-2.0. It adds 80 tokens to every session and 3,643 once invoked, about $0.0004 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
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
release-readiness-check
Verify all prerequisites are met before a release by checking PRs, CI/CD status, environment health, and blocking issues across GitHub, ArgoCD, and Jira. Use before cutting a release, deploying to production, or during release planning.
version-bump
Version the Team plugin at land time (DEV-internal, not distributed): decide the SemVer level, compute the next free version against current main, update all six version strings, cut the [Unreleased] changelog body into a dated [X.Y.Z] section, run the land-time consistency assertion, and commit chore(version): X.Y.Z.…
team-pr
Opens a pull request after verification. Trigger on "open the PR", "open a draft PR", or "/team-pr" only; never infer the phase from passed verification.
changelog
Defines Keep a Changelog updates. Load when the ship phase updates CHANGELOG.md with user-facing changes.