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 agentmods add skills/raphaelmansuy/edgecrab/github-repo-managementnpx skills add raphaelmansuy/edgecrab --skill github-repo-managementgit clone --depth 1 https://github.com/raphaelmansuy/edgecrabWrote 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/raphaelmansuy/edgecrab/github-repo-management)<a href="https://agentmods.dev/skills/raphaelmansuy/edgecrab/github-repo-management"><img src="https://agentmods.dev/badge/skills/raphaelmansuy/edgecrab/github-repo-management.svg" alt="Measured on agentmods" 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 | $0.00047 | $0.03980 |
| Opus 5 | $0.00023 | $0.01990 |
| Sonnet 5 | $0.00009 | $0.00796 |
| Haiku 4.5 | $0.00005 | $0.00398 |
Grade E, and why
github-repo-management scanned grade E with 3 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 5d 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 Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
GH_USER=$(curl -s -H "Authorization: token $GITHUB_TOKEN" https://api.github.com/user | python3 -c "import sys,json; print(json.load(sys.stdin)['login'])") Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl. The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 5d ago First seen · 512 lines · 47 tokens per session scan E 097513197257
github-repo-management is a skill published in the GitHub repository raphaelmansuy/edgecrab (84 stars, last pushed 1mo ago), with no licence file. It adds 47 tokens to every session and 3,980 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it E with 3 findings (reaches for credential files, downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
release
Prepare and publish stable Agent Lightning releases through the repository's version bump, pull-request checks, merge, tag, PyPI trusted-publishing, and versioned-documentation workflows. Use when asked to plan, cut, verify, or explain a release; treat nightly TestPyPI builds as a separate path.
ship-feature
Ship a feature end-to-end — update tests, docs, docs-site, then release to PyPI. Use when user says "ship", "ship feature", "release", or asks to publish a new version.
git-changelog
Use this skill when the task involves generating a changelog, release notes, or commit summary from a Git repository's history. Suitable for tasks like "generate a changelog for v2.0", "summarize what changed since last release", or "create release notes from git commits". Requires access to a Git repository.
release-ops
Use Release Ops when the task is about launch planning, rollout control, release checklists, or go/no-go coordination.
release-manager
Use workflows, boards, hierarchy, and council together when coordinating a release or rollout.
release-notes
Maintain Mozaiks release notes proactively. Use when changing released behavior, preparing a PyPI/GitHub release, bumping versions, modifying generated app scaffolds, changing public install/setup docs, or reviewing whether a change needs a changelog entry.