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 gh-prgit 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/gh-pr)<a href="https://agentmods.dev/skills/zjshen14/opencli/gh-pr"><img src="https://agentmods.dev/badge/skills/zjshen14/opencli/gh-pr/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/gh-pr"><img src="https://agentmods.dev/badge/skills/zjshen14/opencli/gh-pr.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.00027 | $0.00380 |
| Opus 5.5 | $0.00011 | $0.00152 |
| Sonnet 5.5 | $0.00005 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
gh-pr 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 GitHub pull requests for this repository.
Current PR status: !{gh pr status 2>/dev/null || echo "(gh CLI not available or no GitHub remote)"}
Branch context: !{git log --oneline -10 2>/dev/null || echo ""}
Task: $ARGUMENTS
Common operations:
- Create:
gh pr create --title "Title" --body "Body" [--base main] [--draft] [--assignee @me] - View:
gh pr view [<number>] - List:
gh pr list [--state open|closed|merged] [--author <user>] - Check CI:
gh pr checks [<number>] - Review:
gh pr review <number> --approve|--request-changes|--comment --body "..." - Merge:
gh pr merge <number> [--squash|--merge|--rebase] [--delete-branch] - Checkout:
gh pr checkout <number> - Diff:
gh pr diff [<number>]
When creating a PR:
- Title: imperative mood, ≤72 chars (e.g. "Add gh-pr skill")
- Body: summary of changes (what and why), test plan, any breaking changes
- Link the related issue with "Closes #N" or "Part of #N" in the body
- Use
--draftif the work is not yet ready for review - Do not push or create the PR without explicit user approval
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 · 36 lines · 27 tokens per session scan A 5dc31893aa05
gh-pr is a skill published in the GitHub repository zjshen14/opencli (2 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 380 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-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.
05-review
Reviews a change or a diff and says whether it is ready to ship, naming every problem with its fix. Use when the user wants a change checked before it ships. Not for fixing what the review finds, and not for auditing a whole codebase.
review
Use when operating as the Fabrik Review stage agent. This skill guides code review of an implementation, finding and fixing issues, and ensuring the PR is ready for human review.
review-comment
Use when operating as the Fabrik Review comment reviewer. This skill guides applying user decisions on review findings — fixing issues, dismissing false positives, or deferring items — then committing and pushing without signaling stage completion.
pr-gates
This skill should be used when the user asks to "open a PR", "prepare for review", "address review comments", "run gates", or "verify before pushing" in this repository. Enforces preflight/gate workflow, migration safety, and review-evidence closure.
pr-comments
Triage unresolved review threads on an open PR: per thread either agree (fix, verify, push, reply, resolve) or disagree (justify with a version-matched citation). Use when asked about PR comments or told to reply and resolve.