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/zjshen14/opencli/gh-issuenpx skills add zjshen14/opencli --skill gh-issuegit clone --depth 1 https://github.com/zjshen14/opencliWhat 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.00031 | $0.00361 |
| Opus 5 | $0.00015 | $0.00180 |
| Sonnet 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 2d 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.
- 2d 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 9d ago), licensed MIT. It adds 31 tokens to every session and 361 once invoked, about $0.0002 per session on Opus 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-issue-triage
Issue triage and lifecycle management agent for ZeroClaw. Use this skill whenever the user wants to: triage open issues, close stale/duplicate/fixed issues, apply labels, run a backlog sweep, enforce the current issue stale policy, or handle a specific issue. Trigger on: 'triage issues', 'issue triage', 'sweep…
trello
Manages Trello boards, lists, and cards via the Trello REST API. Use when the user wants to create cards, move tasks between lists, list boards, add comments, archive cards, or check what is on a Trello board. Handles authentication, pagination, and rate-limit awareness for all Trello REST endpoints.
aidd-pm:01:ticket-info
Retrieve and display ticket information from the project's configured ticketing tool.
aidd-pm:02:user-stories-create
Generate well-structured user stories from feature requirements through iterative Product Owner questioning.
aidd-async-dev:02:run
Runs one async development pipeline cycle: polls ready GitHub issues, resolves dependencies, locks the issue, delegates implementation to whichever SDLC capability is loaded at runtime, then writes audit log and SIEM webhook. Use when the user (or CI / cron / @claude mention / project board move) says "run async dev"…
room-playbook
Lightweight default rules for coordinating a Room conversation without confusing chat wakeups with durable WorkGraph responsibility.