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/open-curiosity/gini-agent/github-issuesnpx skills add Open-Curiosity/gini-agent --skill github-issuesgit clone --depth 1 https://github.com/Open-Curiosity/gini-agentWhat 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.00034 | $0.04600 |
| Opus 5 | $0.00017 | $0.02300 |
| Sonnet 5 | $0.00007 | $0.00920 |
| Haiku 4.5 | $0.00003 | $0.00460 |
Grade B, and why
github-issues scanned grade B with 2 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo dnf install -y gh # Fedora / RHEL Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: "Create, search, triage, label, assign, comment on, and close GitHub issues using the gh CLI, with a curl REST fallback." How it starts
The opening of the file, as written. The whole thing — 454 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issues
Manage GitHub issues end to end: list, search, view, create, label,
assign, comment, close, reopen, triage, and run bulk operations. Every
section leads with the gh CLI (the preferred path) and follows with a
curl REST fallback for environments where gh is unavailable.
When To Use
- User asks to file, view, search, or update a GitHub issue.
- User asks to triage a backlog ("label the untriaged issues", "assign the open bugs to me").
- User asks for the status of issues on a repo ("what's open on owner/repo", "show me the bugs I'm assigned").
When NOT to Use
- Pull-request review or merge flows → not covered here; use
gh pr …. - Linear, Jira, or other trackers → use their dedicated skill.
- Plain local git history questions → answer with
git logdirectly.
Setup
gh is the preferred path. It must be installed and authenticated before
the first issue operation. Installing is non-interactive — do it
yourself (it's a side-effecting command, so it runs through the approval
seam; you propose it, you don't hand it to the user). Only the interactive
sign-in in step 2 needs the user.
1. Install gh if it's missing
Check for it, and if it's absent, detect the platform and run the matching install command yourself:
command -v gh >/dev/null 2>&1 && echo "gh present: $(gh --version | head -1)"
If that prints nothing, install it:
brew install gh # macOS / Linuxbrew
sudo dnf install -y gh # Fedora / RHEL
sudo pacman -S --noconfirm github-cli # Arch
winget install --id GitHub.cli # Windows
Debian/Ubuntu need the GitHub CLI apt repo added first — run this chain (don't ask the user to):
(type -p wget >/dev/null || (sudo apt update && sudo apt install -y wget)) \
&& sudo mkdir -p -m 755 /etc/apt/keyrings \
&& wget -nv -O- https://cli.github.com/packages/githubcli-archive-keyring.gpg \
| sudo tee /etc/apt/keyrings/githubcli-archive-keyring.gpg >/dev/null \
&& sudo chmod go+r /etc/apt/keyrings/githubcli-archive-keyring.gpg \
&& echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/githubcli-archive-keyring.gpg] https://cli.github.com/packages stable main" \
| sudo tee /etc/apt/sources.list.d/github-cli.list >/dev/null \
&& sudo apt update && sudo apt install -y gh
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 454 lines · 34 tokens per session scan B a50bfee8180d
github-issues is a skill published in the GitHub repository Open-Curiosity/gini-agent (1,761 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 4,600 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
vibelution-continuous-optimization-loop
Runs one evidence-driven Vibelution optimization iteration from the ROI backlog: pick one todo item, worktree isolate, implement, machine-verify, merge, update STATE. Use when the user starts /loop for project improvement, continuous optimization, or agent-dev ROI backlog work.
review
Use when conducting architectural or code quality reviews before merging work.
stale-sweep
Sweep the googleapis/mcp-toolbox repo for issues and PRs with no real activity in N days (default 60), sort each by whose silence it is (the author's, ours, or nobody's), and draft the nudge or close comment. Use whenever a maintainer asks for a stale sweep, backlog cleanup, or an SLO check, e.g. "stale sweep", "find…
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…
backlog-technical-project-manager
Technical project management for Backlog.md workstreams using coordinated sub-agents. Use only when the user explicitly asks Codex to take over one or more existing Backlog.md tasks (for example: "act as TPM", "coordinate these tasks", "delegate to sub-agents"). Orchestrate planning, implementation, and finalization…
goal-conductor
Own a long-horizon goal end to end - decompose it into work items, stand up one top-level session per item, patrol their state on a nudge loop, and decide each next round until the goal is met or a stop condition fires. Use when the user hands over a goal too large for one session ("clear the flaky-test backlog"…