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 zjshen14/opencli --skill branchgit clone --depth 1 https://github.com/zjshen14/opencliWrote 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/zjshen14/opencli/branch)<a href="https://agentmods.dev/skills/zjshen14/opencli/branch"><img src="https://agentmods.dev/badge/skills/zjshen14/opencli/branch/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/zjshen14/opencli/branch"><img src="https://agentmods.dev/badge/skills/zjshen14/opencli/branch.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.00263 |
| Opus 5.5 | $0.00013 | $0.00105 |
| Sonnet 5.5 | $0.00006 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
branch 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
Manage git branches for this repository.
Current branch state: !{git branch -a 2>/dev/null | head -20 || echo "(not a git repo)"}
Open issues (for branch naming): !{gh issue list --limit 10 --json number,title,state 2>/dev/null || echo "(gh CLI not available)"}
Task: $ARGUMENTS
Branch naming convention:
- Feature:
feature/<issue-number>-<short-slug>(e.g.feature/42-add-gh-skills) - Bug fix:
fix/<issue-number>-<short-slug>(e.g.fix/17-loop-on-empty-response) - No issue:
feature/<short-slug>orfix/<short-slug>
Steps:
- Determine the branch name from the task description or issue number
- Create and switch:
git checkout -b feature/42-add-gh-skills - Confirm:
git branch --show-current
If the branch already exists, switch to it: git checkout <branch-name>
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 · 30 lines · 32 tokens per session scan A baae24eedce4
branch is a skill published in the GitHub repository zjshen14/opencli (2 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 263 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-08-31.
Other skills, from other repositories
github-auth
GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login.
github-repo-management
Clone/create/fork repos; manage remotes, releases.
github-issues
Create, triage, label, assign GitHub issues via gh or REST.
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
apply-patch
Apply multi-file or tricky edits atomically with git apply instead of many fragile editfile calls. Use when changing several files at once or when editfile fails to match.