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 IvanCampos/agents --skill githubgit clone --depth 1 https://github.com/IvanCampos/agentsWrote 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/ivancampos/agents/github)<a href="https://agentmods.dev/skills/ivancampos/agents/github"><img src="https://agentmods.dev/badge/skills/ivancampos/agents/github/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/ivancampos/agents/github"><img src="https://agentmods.dev/badge/skills/ivancampos/agents/github.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.00071 | $0.00938 |
| Opus 5.5 | $0.00028 | $0.00375 |
| Sonnet 5.5 | $0.00014 | $0.00188 |
| Haiku 4.5 | $0.00007 | $0.00094 |
Grade A, and why
github 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub CLI
Overview
Use gh for day-to-day GitHub operations from the terminal. Prefer read-only commands first, then run mutating commands only after clear user intent.
Quick Start
- Check installation and auth:
gh --version
gh auth status
- Establish repository context:
scripts/gh_preflight.sh --repo owner/repo
- If not in the target repository, pass
-R owner/repoto commands. - Use
--jsonwith--jqor--templatefor automation-friendly output.
Workflow
- Establish context first.
- Determine GitHub host (
github.comby default), repository, and branch. - Run
scripts/gh_preflight.shbefore multi-step operations.
- Read current state.
- Use
list,view, andstatussubcommands before changing anything.
- Apply requested mutation.
- For create/edit/merge/delete actions, restate the operation and require explicit confirmation unless the user already asked clearly.
- Report stable identifiers.
- Return URLs and IDs for created or changed objects (PR number, issue number, run URL, release tag).
Common Commands
- Repository:
gh repo viewgh repo clone owner/repogh repo creategh repo set-default owner/repo
- Pull requests:
gh pr listgh pr view <number>gh pr checkout <number>gh pr creategh pr review <number> --approve|--request-changes|--commentgh pr merge <number>
- Issues:
gh issue listgh issue view <number>gh issue creategh issue comment <number> --body "..."gh issue close <number>
- Actions:
gh workflow listgh workflow run <workflow>gh run listgh run watch <run-id>gh run view <run-id> --log
- Releases:
gh release listgh release view <tag>gh release create <tag> [assets...]gh release upload <tag> <file>
- API:
gh api repos/{owner}/{repo}/pulls --paginate
For broader command coverage, read references/command-map.md.
Safety Defaults
- Confirm before commands that change remote state:
gh pr create|merge|close|reopen|readygh issue create|edit|close|reopen|deletegh repo create|edit|archive|deletegh release create|edit|deletegh secret set|deletegh variable set|deletegh workflow run
- Avoid destructive flags (
--delete-branch, force flags) unless explicitly requested. - Show exact command before bulk updates and prefer smallest safe scope.
What ships with it
3 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.
- 1mo ago First seen · 102 lines · 71 tokens per session scan A d342bab1d15d
github is a skill published in the GitHub repository IvanCampos/agents (5 stars, last pushed 8mo ago), licensed MIT. It adds 71 tokens to every session and 938 once invoked, about $0.0003 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
github-repo-management
Clone, create, fork repos; manage remotes, releases.
deploy-pipeline-runbook
Use when a release spans multiple systems or vendors, order of operations matters with rollback planned up front, or a failed step in one system could corrupt state in a downstream system.
secret-leak-preflight
Use when about to commit, push, or publish -- staged changes touch config or environment files, generated artifacts (relay sessions, logs, build output) are being added, or the session handled credentials even indirectly.
handoff-discipline
Use when ending a session, handing a task back to the user, or approaching the context limit with work unfinished -- the next session or engineer must be able to resume the work instantly.
pre-release-verification
Use when a release candidate needs final checks before tagging, publishing, or production deployment.
project-release-check
Validate this example project's release readiness. Use before publishing a release candidate.