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 CodeInfinity1/Stram --skill github-repo-managementgit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/github-repo-management)<a href="https://agentmods.dev/skills/codeinfinity1/stram/github-repo-management"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/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/codeinfinity1/stram/github-repo-management"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/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.00032 | $0.00428 |
| Opus 5.5 | $0.00013 | $0.00171 |
| Sonnet 5.5 | $0.00006 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
github-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 1mo 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.
What it actually says
GitHub Repo Management
Purpose
Handle repo administration tasks carefully. Repo management can affect collaboration and release state, so this skill emphasizes verification and explicit user intent.
When To Use
Use for cloning, adding remotes, checking origin/upstream, forking, listing branches, releases, tags, repo metadata, and repo setup diagnosis.
Inputs And Evidence
- Repository URL/path, remote names, branch names, tag/release names, and requested operation.
- Current git status, remotes, auth status, and command output.
Tool Map
run_shell_commandlist_filesread_filesystem_statusgithub-pr-workflow
Workflow
- Confirm target repo and operation.
- Inspect current remotes, branch, and worktree status.
- For read-only tasks, gather evidence with Git/gh commands.
- For mutating tasks, confirm exact target and approval.
- Execute the smallest necessary command.
- Verify resulting remote/branch/tag/release state.
Native Implementation Boundaries
- Use Git/gh through native shell tooling or future Stram GitHub adapters.
- Do not import external reference repo-management scripts.
- Do not use destructive Git commands unless explicitly requested and approved.
Safety And Approval
- Remotes, branches, releases, tags, forks, and deletes can affect collaborators.
- Do not overwrite history without explicit instruction.
- Keep credentials out of command text and notes.
Verification
- Report command output for repo state.
- Verify branch/remote after changes.
- If auth blocks action, report the exact blocker.
Failure Modes
- Managing the parent workspace instead of nested repo.
- Confusing origin and upstream.
- Creating release/tag in the wrong repo.
References
- Shortlist item:
github-repo-management. - Native path: Git/gh through Stram shell tooling.
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.
- 1mo ago First seen · 66 lines · 32 tokens per session scan A 8d5346107a8c
github-repo-management is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 428 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
npm-release
Use when publishing or preparing to publish an npm package from this repository, especially the Skill Zoo CLI package under packages/cli. Also use when npm publish fails because of duplicate versions, npm authentication, browser authentication, dist-tag propagation, tarball contents, bin entry issues, or…
shared-tooling-changesets
Versioning and changelog management with @changesets/cli — adding changesets, version bumping, changelog generation, monorepo publishing, pre-release modes, and CI automation.
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
ship
Commit, push, create PR(s), and auto-finalize — full automation pipeline. Handles uncommitted changes and recently created PRs.
write-changelog
Generates a CHANGELOG.md entry for a release by summarizing git commits since the last tag. Groups changes by type: Added, Changed, Fixed, Removed. Follows Keep a Changelog format (https://keepachangelog.com). Invoked when the user asks to update the changelog, write release notes, or prepare a release.