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 juan294/cc-rpi --skill github-cligit clone --depth 1 https://github.com/juan294/cc-rpiWrote 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/juan294/cc-rpi/github-cli)<a href="https://agentmods.dev/skills/juan294/cc-rpi/github-cli"><img src="https://agentmods.dev/badge/skills/juan294/cc-rpi/github-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/juan294/cc-rpi/github-cli"><img src="https://agentmods.dev/badge/skills/juan294/cc-rpi/github-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.00028 | $0.00887 |
| Opus 5.5 | $0.00011 | $0.00355 |
| Sonnet 5.5 | $0.00006 | $0.00177 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
github-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 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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub CLI
JSON Field Discovery
Wrong -- guess field names:
gh pr checks 42 --json conclusion # Unknown field
Right -- discover fields first:
gh pr checks --help
PR Check Interpretation
Use the documented fields and preserve the command status:
gh pr checks 42 --json name,state,bucket,workflow
# Or watch existing checks to completion:
gh pr checks 42 --watch
Pending checks return exit 8. Exit 1 can mean failed checks or another
command error; inspect output. bucket distinguishes pass, fail,
pending, skipping, and cancel. Do not discard a check merely because
its name is review; inspect its workflow and the repository's requirements.
An empty or incomplete check inventory is not evidence that required CI ran.
These commands inspect existing checks; they do not authorize PR creation.
See the GitHub CLI manual.
Release vs PR Flags
Wrong -- --body is for pr/issue create, not release:
gh release create v1.0.0 --body "notes"
Right -- releases use --notes:
gh release create v1.0.0 --notes "notes"
Label and Merge Settings
Wrong -- assume labels exist and merge method is allowed:
gh issue create --label "chore" --title "Fix" # label not found
gh pr merge 42 --merge # method not allowed
Right -- check or create first:
gh label list && gh label create "chore" --color "ededed"
gh api repos/{owner}/{repo} --jq '.allow_squash_merge, .allow_merge_commit'
When creating multiple issues, create them sequentially, not as parallel
tool calls -- a batch of parallel gh issue create calls that all hit the
same missing label fail together instead of surfacing once.
Deprecated Projects (Classic) API
Wrong -- an older gh version queries a removed field and errors:
gh issue view 42 --json projectCards # Projects (classic) is deprecated
Right -- upgrade gh first:
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 Changed · +5 lines a90bb082cdec
- 1mo ago First seen · 134 lines · 28 tokens per session scan A df092250fbd9
github-cli is a skill published in the GitHub repository juan294/cc-rpi (5 stars, last pushed 7d ago), licensed MIT. It adds 28 tokens to every session and 887 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
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…
studio-source-control
Drive a scoped application's linked git repository from the instance — what has to be true before Source Control works at all, the commit-then-push order, stashes and branches over /api/snsourcecontrol, and when this replaces update sets rather than sitting next to them.
git-workflow
Helps with git workflows including conventional commit messages, branching strategies, merge conflict resolution, and changelog generation. Triggers on: "git commit message", "branching strategy", "resolve conflict", "generate changelog".
repo-delivery
Execute authorized Git commits, pushes, integration, history changes, or cleanup.
ship
Use when a change is ready to land. Runs the full sequence — branch, quality gate, commit, push, PR — so nothing gets skipped.
git-onboarding-auto
A Git setup and pull-request workflow automation skill. Git is the version-control tool developers use to track code changes, while a pull request is a request for teammates to review and merge those changes.