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-issuegit 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-issue)<a href="https://agentmods.dev/skills/zjshen14/opencli/gh-issue"><img src="https://agentmods.dev/badge/skills/zjshen14/opencli/gh-issue/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-issue"><img src="https://agentmods.dev/badge/skills/zjshen14/opencli/gh-issue.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.00031 | $0.00361 |
| Opus 5.5 | $0.00012 | $0.00144 |
| Sonnet 5.5 | $0.00006 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
gh-issue 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 issues for this repository.
Current open issues: !{gh issue list --limit 10 --json number,title,state,labels 2>/dev/null || echo "(gh CLI not available or no GitHub remote)"}
Recent commits for context: !{git log --oneline -5 2>/dev/null || echo ""}
Task: $ARGUMENTS
Common operations:
- Create:
gh issue create --title "Title" --body "Body" [--label bug,enhancement] [--assignee @me] - View:
gh issue view <number> - List:
gh issue list [--state open|closed|all] [--label <label>] [--assignee <user>] - Comment:
gh issue comment <number> --body "Comment" - Close:
gh issue close <number> [--comment "Reason"] - Edit:
gh issue edit <number> [--title "New title"] [--body "New body"] [--add-label <label>]
When creating an issue:
- Draft a concise title in plain language (not imperative — describes the problem or feature, ≤72 chars)
- Write a structured body: context/motivation, steps to reproduce (bugs) or acceptance criteria (features), any relevant code snippets
- Apply appropriate labels if they exist in the repo (
gh label list) - Confirm with the user before submitting unless they said "just do it"
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 · 33 lines · 31 tokens per session scan A b5a84e3f09e6
gh-issue is a skill published in the GitHub repository zjshen14/opencli (2 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 361 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
linear
Linear: manage issues, projects, teams via GraphQL + curl.
github-issues
Create, triage, label, assign GitHub issues via gh or REST.
hive.colony-progress-tracker
Claim tasks, record step progress, and verify SOP gates in the colony SQLite queue. Applies when your spawn message includes a dbpath field.
linear-tickets
Create or update high-quality Linear tickets while preserving the originating report, diagnostic links, attachments, and reporter/requester attribution. Read this whenever someone asks to create, recreate, or update a Linear issue.
status-report
Use when the user asks for a weekly / monthly status report, project update, individual or team progress summary. Produces a tight, scannable update with what shipped, what's in flight, what's blocked, and metrics.
awesome-ai-agents-curation
Help founders prepare evidence-backed AI agent project submissions and help maintainers triage project issues and pull requests for the Awesome AI Agents list.