Routa is a workspace-based coordination platform for delivering software with multiple AI agents, keeping goals, tasks, sessions, traces, evidence, and review decisions visible on a shared board. It is intended for teams managing agent-assisted development across web and desktop applications. The catalogue contains skills and instructions for working with Routa's delivery workflows.
Borrowing it
Nothing to install: this file belongs to phodal/routa. 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/phodal/routa/main/.agents/skills/release/SKILL.mdgit clone --depth 1 https://github.com/phodal/routaWrote 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/phodal/routa/release)<a href="https://agentmods.dev/skills/phodal/routa/release"><img src="https://agentmods.dev/badge/skills/phodal/routa/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/phodal/routa/release"><img src="https://agentmods.dev/badge/skills/phodal/routa/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.00038 | $0.00511 |
| Opus 5.5 | $0.00015 | $0.00204 |
| Sonnet 5.5 | $0.00008 | $0.00102 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
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 1mo 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.
What it actually says
Prepare Routa releases with the existing repo scripts. Keep the workflow deterministic until human confirmation is needed for commit, tag, or push.
When to use
- The user asks to release Routa, publish a version, prepare release notes, or generate a release blog post.
- The task needs synchronized version bumps plus
docs/releases/artifacts.
Workflow
- Confirm the target version and whether the user wants a dry run or an actual publish.
- If a release summary already exists, pass it with
--summary-file. If the user wants AI-generated summary copy, add--aiand optionally--ai-provider <name>. - Run the helper:
node scripts/release/prepare-release-artifacts.mjs <version>
node scripts/release/prepare-release-artifacts.mjs <version> --from <previous-tag> --ai --ai-provider claude
- Review the generated files:
docs/releases/v<version>-release-notes.mddocs/releases/v<version>-changelog.mddist/release/changelog-summary-prompt.json
- If the user only wants preparation, stop after review and validation.
- If the user wants to publish, continue with either:
./scripts/release/publish.sh <version>
or the manual flow documented in docs/release-guide.md.
Guardrails
- Do not tag or push without explicit user confirmation.
- Do not discard unrelated worktree changes.
- Prefer
docs/releases/v<version>-release-notes.mdas the blog/release-note source of truth after generation. - If
git status --porcelainis not clean and the task is a real publish, call that out before invokingpublish.sh.
References
- Read
references/release-workflow.mdfor the step-by-step release decision tree. - Read
docs/release-guide.mdwhen the task needs the full publish or verification checklist.
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.
- 1mo ago First seen · 56 lines · 38 tokens per session scan A 0e5545c82250
release is a skill published in the GitHub repository phodal/routa (1,830 stars, last pushed 14d ago), licensed MIT. It adds 38 tokens to every session and 511 once invoked, about $0.0002 per session on Opus 5.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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.