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 Knuckles-Team/repository-manager --skill repository-manager-workspace-releasegit clone --depth 1 https://github.com/Knuckles-Team/repository-managerWrote 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/knuckles-team/repository-manager/repository-manager-workspace-release)<a href="https://agentmods.dev/skills/knuckles-team/repository-manager/repository-manager-workspace-release"><img src="https://agentmods.dev/badge/skills/knuckles-team/repository-manager/repository-manager-workspace-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/knuckles-team/repository-manager/repository-manager-workspace-release"><img src="https://agentmods.dev/badge/skills/knuckles-team/repository-manager/repository-manager-workspace-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00188 | $0.02094 |
| Opus 5.5 | $0.00075 | $0.00838 |
| Sonnet 5.5 | $0.00038 | $0.00419 |
| Haiku 4.5 | $0.00019 | $0.00209 |
Grade A, and why
repository-manager-workspace-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 7d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Manager — Workspace Release
Releasing a workspace is validate → bump → push, phased over a topologically
ordered dependency graph declared in workspace.yml's maintenance config (lower
phase = more upstream; a change in phase N only ever cascades to phases >= N,
never backward — CONCEPT:RM-PHASE-START/CONCEPT:RM-BUMP). This skill is about
running that safely and previewing it before anything mutates, not about what
"valid" means per project (that is repository-manager-workspace-validation) or
how a push actually executes (repository-manager-bulk-git-operations).
When to use
- Preview which repos would bump/push before running anything (
dry_run). - Run the full validate → consented-bump → consented-push chain in one call.
- Bump versions across the dependency-ordered workspace on their own.
- Scaffold, template, save, or list the
workspace.ymlmanifest.
When NOT to use
- Per-project validation semantics (pre-commit + pytest pass/fail) →
repository-manager-workspace-validation. - The actual
rm_git_phased_pushmechanics and bulk clone/pull/push →repository-manager-bulk-git-operations. - Candidate/generation certification for one branch landing →
repository-manager-candidate-certification.
Tools & actions
| Tool group | Per-operation tools relevant here |
|---|---|
rm_workspace_* |
rm_workspace_fleet_evidence_check, rm_workspace_maintain, rm_workspace_maintain_status, rm_workspace_list, rm_workspace_list_branches, rm_workspace_setup, rm_workspace_template, rm_workspace_save |
rm_projects_validate, rm_projects_validate_status (the consented bump/push chain lives here — see below) |
CLI: repository-manager --maintain --bump {patch,minor,major} [--phase N] [--single-phase] [--no-auto-start] [--project <name>] [--dry-run] [--allow-pre-commit] [--config <path>], and separately --validate [--bump ...] [--push] for the validate-then-release chain, or --push alone for phased push
only.
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.
- 7d ago Changed · +3 tokens per session e75169e1875c
- 23d ago Changed 3445356c16f5
- 1mo ago First seen · 160 lines · 185 tokens per session scan A 3f00868b3161
repository-manager-workspace-release is a skill published in the GitHub repository Knuckles-Team/repository-manager (3 stars, last pushed yesterday), licensed MIT. It adds 188 tokens to every session and 2,094 once invoked, about $0.0008 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-31.
Other skills, from other repositories
Release Notes Generator
Generate professional software release notes from a commit log: classify changes, write user-facing summaries, draft a publishable announcement, and assess release readiness. Use for release, changelog, version, and deploy requests.
Release Readiness Reviewer
Reviews a release candidate and produces a go/no-go readiness decision.
Release Checklist
Check release readiness and record a release note. Use for release and rollback requests.
plugin-publish
A release guide for publishing Zhin.js plugins to npm, the JavaScript package registry, and to the Zhin plugin marketplace. It covers package metadata, versioning, release checks, and submission requirements.
github-repo-care
Protocol for safely creating, publishing, releasing, auditing, and maintaining GitHub repositories: check local rules and locks, create .gitignore before the first add, run privacy checks, prepare README/i18n/banner/metadata, verify release tags and GitHub releases, and update organization profiles, llms.txt files…
metagit-projects
Ongoing workspace and project management for OpenClaw and Hermes agents. Use when starting work, organizing repos, or before creating a new project folder so existing metagit projects are reused instead of duplicated.