Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/AmineDjeghri/personal-os-setupnpx agentmods add skills/aminedjeghri/personal-os-setup/github-repo-managementWrote 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/aminedjeghri/personal-os-setup/github-repo-management)<a href="https://agentmods.dev/skills/aminedjeghri/personal-os-setup/github-repo-management"><img src="https://agentmods.dev/badge/skills/aminedjeghri/personal-os-setup/github-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/aminedjeghri/personal-os-setup/github-repo-management"><img src="https://agentmods.dev/badge/skills/aminedjeghri/personal-os-setup/github-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.00017 | $0.01458 |
| Opus 5.5 | $0.00007 | $0.00583 |
| Sonnet 5.5 | $0.00003 | $0.00292 |
| Haiku 4.5 | $0.00002 | $0.00146 |
Grade C, and why
github-repo-management scanned grade C with 2 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 18d 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
gh secret set SSH_KEY < ~/.ssh/id_rsa Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Action | gh | git + curl | This is a copy
83% identical to github-repo-management — 358 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Repository Management
Create, clone, fork, configure, and manage GitHub repositories.
No gh? Install it (see github-auth) — genuine fallback: references/rest-api-fallback.md.
Prerequisites
ghauthenticated with GitHub (see thegithub-authskill).$GH_USERbelow comes fromgh api user --jq .login.
1. Cloning Repositories
Cloning is pure git — works identically either way:
# Clone via HTTPS (works with credential helper or token-embedded URL)
git clone https://github.com/owner/repo-name.git
# Clone into a specific directory
git clone https://github.com/owner/repo-name.git ./my-local-dir
# Shallow clone (faster for large repos)
git clone --depth 1 https://github.com/owner/repo-name.git
# Clone a specific branch
git clone --branch develop https://github.com/owner/repo-name.git
# Clone via SSH (if SSH is configured)
git clone [email protected]:owner/repo-name.git
gh repo clone owner/repo-name
gh repo clone owner/repo-name -- --depth 1
2. Creating Repositories
# Create a public repo and clone it
gh repo create my-new-project --public --clone
# Private, with description and license
gh repo create my-new-project --private --description "A useful tool" --license MIT --clone
# Under an organization
gh repo create my-org/my-new-project --public --clone
# From existing local directory
cd /path/to/existing/project
gh repo create my-project --source . --public --push
From a Template
gh repo create my-new-app --template owner/template-repo --public --clone
3. Forking Repositories
gh repo fork owner/repo-name --clone
Keeping a Fork in Sync
# Pure git — works everywhere
git fetch upstream
git checkout main
git merge upstream/main
git push origin main
gh repo sync $GH_USER/repo-name
4. Repository Information
gh repo view owner/repo-name
gh repo list --limit 20
gh search repos "machine learning" --language python --sort stars
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.
- 18d ago Changed · -318 lines scan E → C 22c7fb06ea4b
- 27d ago First seen · 517 lines · 17 tokens per session scan E 7b528746118c
github-repo-management is a skill published in the GitHub repository AmineDjeghri/personal-os-setup (654 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 1,458 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (reaches for credential files, makes network calls). It is 83% identical to github-repo-management, differing in 358 lines, and is treated as a copy.
Other skills, from other repositories
release-manager
Prepare and publish a Local Coding Agent release with tests, version bump, tag, GitHub Release notes, and optional assets.
release-helper
Prepare a safe Local Coding Agent release build, including version checks, tests, and changelog.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.