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 darellchua2/opencode-config-template --skill gh-cli-setup-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/darellchua2/opencode-config-template/gh-cli-setup-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/gh-cli-setup-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/gh-cli-setup-skill/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/darellchua2/opencode-config-template/gh-cli-setup-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/gh-cli-setup-skill.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.00076 | $0.00725 |
| Opus 5.5 | $0.00030 | $0.00290 |
| Sonnet 5.5 | $0.00015 | $0.00145 |
| Haiku 4.5 | $0.00008 | $0.00072 |
Grade B, and why
gh-cli-setup-skill scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
| Debian/Ubuntu | `sudo apt update && sudo apt install -y gh` (needs `gh` apt repo on older images: see https://github.com/cli/cli/blob/trunk/docs/install_linux.md) | How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
Set up the GitHub CLI so ticket- and PR-creation flows can continue in
environments where gh is missing or unauthenticated. I am the fallback
referenced by ticket-creation-skill (§Prerequisites, §Common Issues) and
pr-creation-workflow-skill (step 6): they invoke me when
command -v gh fails, then resume their flow.
When to use me
command -v ghfails inside a ticket/PR flowghinstalled butgh auth statusis not valid- Fresh machine setup before any GitHub operation
Steps
1. Verify absence
command -v gh || echo "MISSING"
gh auth status 2>&1 || true
If gh exists and is authenticated, return to the calling flow — nothing to do.
2. Install per OS
| OS | Command |
|---|---|
| macOS | brew install gh |
| Debian/Ubuntu | sudo apt update && sudo apt install -y gh (needs gh apt repo on older images: see https://github.com/cli/cli/blob/trunk/docs/install_linux.md) |
| Fedora/RHEL | sudo dnf install -y gh |
| Windows | winget install --id GitHub.cli (or choco install gh) |
Confirm: gh --version.
3. Authenticate
gh auth login
Device flow is the default for headless/SSH environments: pick
GitHub.com → SSH protocol (matches this config's git operations) →
Login with a web browser, then open https://github.com/login/device and
enter the one-time code. In a browser-less session, gh auth login
prints the code and URL regardless — copy it to the user.
4. Verify
gh auth status
✓ Logged in to github.com account <login>→ done; report the login and return to the calling flow.- Token present but missing
reposcope → re-auth withgh auth refresh -s repo(ticket/PR creation requiresrepo); if the refresh fails, redo step 3.
Common Issues
- No browser available — the device flow works from any second device; hand the user the code + URL.
ghnot found after install — new install path not on$PATH;hash -r(bash) or reopen the shell.- Corporate proxy — export
HTTPS_PROXYbeforegh auth login.
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 · 86 lines · 76 tokens per session scan B c5ab8a827137
gh-cli-setup-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed 28d ago), licensed Apache-2.0. It adds 76 tokens to every session and 725 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-19.
Other skills, from other repositories
git-ship
An automated Git release workflow that takes code changes through a branch, commit, pull request, review checks, squash merge, and return to the main branch. A pull request is a request to review and merge changes into a shared branch.
jig-github-sync
Use when synchronizing this repository's GitHub setup: main/develop branches, optional branch protection, and the managed local guards (the git pre-push hook plus the native Codex and Antigravity push hooks), including guard cleanup before uninstalling jig. Do not use for creating a release.
jig-version-rubric
Use when creating, reviewing, or re-setting this repository's version grading rubric at .jig/versioning.md: adopt the jig default human-intervention rubric, write a project-specific one, edit one grade, or reset to the default. Owns the rubric file; never runs a release.
jig-develop-task-flow
Use for ordinary implementation tasks in a repository that has adopted the jig develop/main model: start from develop, create a feature/fix/chore branch, complete changes and tests, squash-merge back into develop locally, and push develop. No pull requests. Execution scope comes from the current request and explicitly…
jig-github-release
Use when releasing this repository from the CLI by promoting develop to main with a fast-forward push, grading the release as patch/minor/major by what installed projects actually pay, computing the next version from the latest tag, and publishing a GitHub release with agent-written notes. No release PR, no…
jig-hotfix-flow
Use when a released defect on main must ship before the work already sitting on develop. Branches from main, lands one squashed commit on main through the guard-allowed hotfix push, tags and publishes, then merges main back into develop so the next release still fast-forwards.