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.00176 | $0.02497 |
| Opus 5 | $0.00088 | $0.01248 |
| Sonnet 5 | $0.00035 | $0.00499 |
| Haiku 4.5 | $0.00018 | $0.00250 |
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 8d 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 — 141 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
condensed 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.
- 8d 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 (2 stars, last pushed 11d ago), licensed MIT. It adds 176 tokens to every session and 2,497 once invoked, about $0.0009 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-31.
Other skills, from other repositories
drain
Parallel-worktree auto-drain of the board. One /super-bootstrap:drain turn = scan the pipeline sources (specs/plans/backlog, plus the scale module's test queue when present) → keep only admissible items → relation-analyze into a conflict-free wave → confirm with the user → spawn one isolated git worktree + headless…
git-worktree-manager
Manage git worktrees for isolated branch development - create, list, switch, and clean up worktrees for parallel feature development, safe experimentation, and CI/CD isolation.
worktree-lifecycle
Use when starting isolated feature work or before executing implementation plans. Manages full worktree lifecycle from creation through cleanup with safety checks and error recovery.
github-integration
A coding aid for working with GitHub, a service for hosting code and coordinating software work. It supports creating and querying issues and pull requests and retrieving repository information.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.