Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/contactandrewchl-wq/turtle-mcpnpx agentmods add skills/contactandrewchl-wq/turtle-mcp/gh-cliWrote 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/contactandrewchl-wq/turtle-mcp/gh-cli)<a href="https://agentmods.dev/skills/contactandrewchl-wq/turtle-mcp/gh-cli"><img src="https://agentmods.dev/badge/skills/contactandrewchl-wq/turtle-mcp/gh-cli/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/contactandrewchl-wq/turtle-mcp/gh-cli"><img src="https://agentmods.dev/badge/skills/contactandrewchl-wq/turtle-mcp/gh-cli.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.00060 | $0.00999 |
| Opus 5 | $0.00030 | $0.00500 |
| Sonnet 5 | $0.00012 | $0.00200 |
| Haiku 4.5 | $0.00006 | $0.00100 |
Grade A, and why
gh-cli 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub CLI (gh)
Cuándo usar
- Abrir o revisar un PR.
- Chequear estado de CI o logs de un run fallido.
- Crear o triagear issues.
- Hacer una llamada cruda a la API de GitHub sin escribir cURL.
Setup mínimo
gh auth status # ¿estás logueado?
gh auth login # OAuth interactivo si no lo estás
gh repo set-default # fijar el repo "current" del directorio
Pull requests
# Crear PR desde la rama actual (abre editor; --fill toma title/body del commit)
gh pr create --base main --fill
gh pr create --title "feat: x" --body-file PR_BODY.md
# Listar y filtrar
gh pr list --state open --author "@me"
gh pr list --label bug --assignee "@me"
# Ver detalle / diff / checks
gh pr view 123
gh pr view 123 --web # abrir en navegador
gh pr diff 123
gh pr checks 123
# Revisar
gh pr review 123 --approve -b "LGTM"
gh pr review 123 --request-changes -b "Ver comentarios"
gh pr comment 123 -b "Texto"
# Merge (squash por defecto en muchos repos)
gh pr merge 123 --squash --delete-branch
gh pr merge 123 --merge # commit de merge
gh pr merge 123 --rebase # rebase
Issues
gh issue list --state open --label bug
gh issue create --title "..." --body "..." --label bug --assignee "@me"
gh issue view 42
gh issue comment 42 -b "Texto"
gh issue close 42 --reason "not planned"
CI / runs
gh run list # últimos workflow runs
gh run list --workflow=ci.yml --branch main
gh run view <run-id> # detalle
gh run view <run-id> --log # logs completos
gh run view <run-id> --log-failed # solo lo que falló
gh run rerun <run-id> # reintentar
gh run rerun <run-id> --failed # solo jobs fallidos
gh run watch <run-id> # esperar a que termine
Releases
gh release create v1.2.0 --generate-notes
gh release create v1.2.0 ./dist/* --notes "Cambios..."
gh release list
gh release view v1.2.0
gh release upload v1.2.0 ./dist/extra.tar.gz
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.
- 8d ago First seen · 132 lines · 60 tokens per session scan A bfe6b792d752
gh-cli is a skill published in the GitHub repository contactandrewchl-wq/turtle-mcp (2 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 999 once invoked, about $0.0003 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
pi-package-sandbox-test
Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.
github
GitHub CLI (gh) for repository management, issues, pull requests, releases, workflows, search, gists, and API access. Use when the user asks about any GitHub operation — creating repos, forking, cloning, PR workflows, issue triage, CI/CD runs, code search, release management, or direct API calls. Keywords: github, gh…
git
Run git version control commands for repository management. Use when the user asks to check status, view history or diffs, stage and commit changes, manage branches, merge or rebase, work with remotes, stash changes, tag releases, cherry-pick commits, bisect regressions, resolve conflicts, manage worktrees or…
changelog-generator
Generate a polished CHANGELOG.md and release-notes.md from a local git repository (or a captured .git-log.txt dump). Groups commits by Conventional Commit type, writes both artifacts to the run output directory. Use when asked to draft release notes, summarize commits between tags, or produce a human-readable…
pi-release-workflow
Use when preparing or validating Pi monorepo releases, including Changesets, pnpm lockfile updates, package previews, release-age policy, and installability checks.
pi-review-gated-delivery
Use when coordinating review-gated delivery of discrete GitHub issues between one implementation peer and a review-only lead, with user-owned Changesets and approval-gated commits.