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 skills add tanbro/uiautomator2-mcp-server --skill release-managergit clone --depth 1 https://github.com/tanbro/uiautomator2-mcp-serverWrote 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/tanbro/uiautomator2-mcp-server/release-manager)<a href="https://agentmods.dev/skills/tanbro/uiautomator2-mcp-server/release-manager"><img src="https://agentmods.dev/badge/skills/tanbro/uiautomator2-mcp-server/release-manager/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/tanbro/uiautomator2-mcp-server/release-manager"><img src="https://agentmods.dev/badge/skills/tanbro/uiautomator2-mcp-server/release-manager.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.00037 | $0.01749 |
| Opus 5.5 | $0.00015 | $0.00700 |
| Sonnet 5.5 | $0.00007 | $0.00350 |
| Haiku 4.5 | $0.00004 | $0.00175 |
Grade A, and why
release-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 2mo 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Manager Skill
⚠️ CRITICAL: Git Tag Timing & Branch Management
MOST IMPORTANT: Git tagging MUST happen at the EXACT LAST MOMENT before pushing to remote, on the main/master branch ONLY.
The Absolute Rule
Git tag creation is the FINAL step before pushing - nothing comes after it except git push.
Tag Timing Rules
❌ WRONG: Tag during development/testing phase ❌ WRONG: Tag before final validation ❌ WRONG: Tag before merging to main/master ❌ WRONG: Tag on develop branch ❌ WRONG: Tag → then discover uncommitted files ❌ WRONG: Tag → then realize tests need to run ✅ CORRECT: All work complete → Merged to main/master → Tag (FINAL STEP) → Push
Branch Management Rules
- Development happens on:
developbranch - Release commits created on:
developbranch - Merge direction:
develop→main(ormaster) - Tag location:
main(ormaster) branch ONLY - Push order: Push main branch, then push tag
Why this matters:
- Premature tagging creates broken releases where the tag points to incomplete/untested code
- Tags on wrong branches cause version confusion and deployment issues
- Proper branch isolation ensures clean release history
- Tagging as the final step guarantees the tagged commit is exactly what gets published
Goals
- Automate the complete release workflow from evaluation to publication
- Ensure code quality and documentation completeness before release
- Provide interactive release management with human oversight
- Support both standard and emergency release scenarios
- CRITICALLY: Enforce proper git tag timing to prevent broken releases
Prerequisites
- Git repository with proper remote configuration
- Python development environment with required tools installed
- GitHub account with repository access permissions
- Proper version control setup (main/develop branches)
- Pre-commit hooks configured and working
Release Workflow Phases
Phase 1: Codebase Evaluation
- Assess current Git status and branch position
- Review recent commits and changes since last release
- Check version numbers and changelog entries
- CRITICAL: Verify all untracked files are handled (committed or .gitignore'd)
- Verify working directory is clean (no uncommitted changes)
- Evaluate overall project health and readiness
What ships with it
3 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.
- 2mo ago First seen · 203 lines · 37 tokens per session scan A 1de7bf676943
release-manager is a skill published in the GitHub repository tanbro/uiautomator2-mcp-server (54 stars, last pushed 4d ago), licensed Apache-2.0. It adds 37 tokens to every session and 1,749 once invoked, about $0.0001 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
version-bump
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. npm publishing is done by the tag-triggered GitHub Actions workflow through…
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
release
Fully automate a release with version-bump and childhood.
team-release
Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.
operating-github-cli
Default GitHub skill for the action agent. Use githubcli for any GitHub request — create/list/view/close issues and PRs, assign, labels, repos, releases, checks, github.com/owner/repo URLs, or gh api. Prefer over shellrun/!gh. Run these with githubcli in the current agent turn.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.