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-development-lifecyclegit 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-development-lifecycle)<a href="https://agentmods.dev/skills/knuckles-team/repository-manager/repository-manager-development-lifecycle"><img src="https://agentmods.dev/badge/skills/knuckles-team/repository-manager/repository-manager-development-lifecycle/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-development-lifecycle"><img src="https://agentmods.dev/badge/skills/knuckles-team/repository-manager/repository-manager-development-lifecycle.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.00180 | $0.02579 |
| Opus 5.5 | $0.00072 | $0.01032 |
| Sonnet 5.5 | $0.00036 | $0.00516 |
| Haiku 4.5 | $0.00018 | $0.00258 |
Grade A, and why
repository-manager-development-lifecycle 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Manager — Development Lifecycle
The governed entrypoint for one unit of work: one agent session or one person, taking one repository from "nothing started" to "landed", without ever touching a canonical checkout, a raw shell command, a shared cargo target, or a hand-merge.
This skill invents nothing. Every step below is a named action on an existing
per-operation tool (rm_lane_*, rm_worktree_*, rm_merge_queue_*, rm_concepts_*) —
confirmed against repository_manager/mcp_tools/contracts.py,
repository_manager/lane_doctor.py, and the CLI parser
(repository_manager/cli_commands/parser.py) on main. Where the brief's
lifecycle name (heartbeat) does not correspond to a callable action, this skill
says so explicitly rather than inventing one — see step 3.
When to use
- Start here for any change an agent will eventually land into a shared base.
- You need the whole arc — open isolation, work safely, prove readiness, hand off, watch it land, or cleanly back out — not just one raw verb.
When NOT to use
- Fan-out across many repositories or a whole wave of lanes →
repository-manager-fleet-scale-operations. - Bulk clone/pull/push/commit across repos with no single lane around it →
repository-manager-bulk-git-operations. - Content-addressed build/cache mechanics →
repository-manager-build-coordination. - Candidate/generation certification detail beyond "is my branch ready" →
repository-manager-candidate-certification. - Registering or dispatching to a remote worker host →
repository-manager-worker-operations. - Reserving/materializing a concept id in detail beyond step 1 below →
repository-manager-concept-coordination. - Workspace-wide version/release planning →
repository-manager-workspace-release. - Raw worktree/merge-queue verbs with no lifecycle narrative →
repository-manager-worktree-orchestration/repository-manager-merge-and-reconcile. Those skills document the same tools at the mechanism level; this one documents the sequence an implementation agent should actually run.
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 Changed · +4 tokens per session 10949c7dceab
- 26d ago Changed · +7 lines 0d4253520bec
- 2mo ago First seen · 141 lines · 176 tokens per session scan A 891b742980ad
repository-manager-development-lifecycle is a skill published in the GitHub repository Knuckles-Team/repository-manager (3 stars, last pushed yesterday), licensed MIT. It adds 180 tokens to every session and 2,579 once invoked, about $0.0007 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
gh
GitHub CLI skill for interacting with GitHub via the gh command line tool. Use when Bub needs to (1) Create, view, or manage GitHub repositories, (2) Work with issues and pull requests, (3) Create and manage releases, (4) Run and monitor GitHub Actions workflows, (5) Create and manage gists, (6) Install and manage…
stacking-prs
Create and manage GitHub native Stacked PRs in this repo with the gh stack CLI. Use when asked to stack PRs, split a large change into a stack, add a layer to a stack, restack or rebase a stack, adopt existing branches or PRs into a stack, check out someone else's stack, or land a stack. Covers creating and submitting…
spawnpoint
This skill should be used when an agent needs to create, list, extend, or remove multi-repo git worktree workspaces using the spawnpoint CLI (binary spawnpoint, shell wrapper sp). Use it when a task involves spinning up isolated worktrees for a feature branch across one or more repos, finding existing workspaces…
daf-workflow
DevAIFlow session context loader — reads session metadata, issue tracker tickets, and context files. Auto-activates when DAFSESSIONNAME is set. Also useful when asked about current task, session status, or workflow steps for daf open, daf new, daf git new, daf jira new, and daf investigate.
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.
metagit-rewrite-campaign
Orchestrate a reference-implementation rewrite across source and target repos using campaigns, parity registry conventions, objectives, and subagent handoffs.