Borrowing it
Nothing to install: this file belongs to abuango/pos-ai. 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/abuango/pos-ai/main/.claude/skills/repo-management/SKILL.mdgit clone --depth 1 https://github.com/abuango/pos-aiWrote 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/abuango/pos-ai/repo-management)<a href="https://agentmods.dev/skills/abuango/pos-ai/repo-management"><img src="https://agentmods.dev/badge/skills/abuango/pos-ai/repo-management/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/abuango/pos-ai/repo-management"><img src="https://agentmods.dev/badge/skills/abuango/pos-ai/repo-management.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.00051 | $0.01181 |
| Opus 5 | $0.00026 | $0.00590 |
| Sonnet 5 | $0.00010 | $0.00236 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade A, and why
repo-management 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Management
Setup
Before starting: check .handoff/sessions/ for active sessions, read context status.yaml, run git status. Follow .rules/universal.md (Plan -> Approve -> Execute).
Wrapper for scripts/repo-manager.sh to manage git repositories across teams.
Commands
/repo setup {team|--all}- Clone all repos for a team/repo sync {team|--all}- Pull latest changes/repo status {team|--all}- Check repo status/repo verify {team|--all}- Verify repos are cloned/repo list {team|--all}- List repos for team/repo teams- List all teams/repo branch {team} {type/name}- Create branch across repos/repo merge {team}- Merge current to active branch/repo cleanup {team} [--dry-run] [--remote]- Delete merged branches
Branch Strategy
All teams use develop as active branch, main/master is production-only.
Full SOP: docs/system/sops/branch-strategy.md
The sync command automatically enforces this: repos on main/master get switched to develop.
The status command shows [WARN: should be on develop] for repos on the wrong branch.
Available Contexts
Contexts are defined in pos.yaml under the contexts: key. Run /repo teams to list all registered contexts with repositories.
Process
Execute Command
All commands execute the repo-manager.sh script:
scripts/repo-manager.sh {command} {args}
/repo setup {team}
Clones all repositories for a team from the platform registry.
./scripts/repo-manager.sh setup {team}
# Or for all teams:
./scripts/repo-manager.sh setup --all
What it does:
- Reads platform-registry.yaml for team repos
- Clones each repo to
{teams_dir}/{team}/repos/ - Checks out the active branch (if different from default)
- Reports success/failure for each repo
/repo sync {team}
Pulls latest changes for all team repos.
./scripts/repo-manager.sh sync {team}
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.
- 11d ago First seen · 176 lines · 51 tokens per session scan A 0d76b69d2b40
repo-management is a skill published in the GitHub repository abuango/pos-ai (2 stars, last pushed 5mo ago), licensed MIT. It adds 51 tokens to every session and 1,181 once invoked, about $0.0003 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…