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 adampoit/ai --skill ghgit clone --depth 1 https://github.com/adampoit/aiWrote 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/adampoit/ai/gh)<a href="https://agentmods.dev/skills/adampoit/ai/gh"><img src="https://agentmods.dev/badge/skills/adampoit/ai/gh/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/adampoit/ai/gh"><img src="https://agentmods.dev/badge/skills/adampoit/ai/gh.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.00051 | $0.00738 |
| Opus 5.5 | $0.00020 | $0.00295 |
| Sonnet 5.5 | $0.00010 | $0.00148 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
gh 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gh
Use gh for GitHub-related tasks.
gh pr view 123 --json number,title,body,commits,files,headRefName,url
Inspect PRs And Issues
View one PR as JSON:
gh pr view 123 --json number,title,body,commits,files,headRefName,url
List open PRs:
gh pr list --state open --json number,title,headRefName,url
View one issue as JSON:
gh issue view 456 --json number,title,body,comments,url
Search GitHub
Prefer gh search for code/repo/issue/PR discovery.
Code search:
gh search code "TODO repo:owner/repo path:src" --limit 20
Repository search:
gh search repos "topic:cli language:go" --limit 20 --json name,description,url
Issue search:
gh search issues "repo:owner/repo is:issue is:open label:bug" --limit 50 --json number,title,url,state,updatedAt
PR search:
gh search prs "repo:owner/repo is:pr is:open author:alice" --limit 50 --json number,title,url,state,updatedAt
Search tips:
- Use qualifiers to reduce noise:
repo:,path:,language:,is:open,author:,label: - Start broad, then refine filters
- Combine with local search (
rg) in checked-out repos when validating context
Checks And CI
View checks for a PR branch:
gh pr checks 123
View run details with links:
gh run list --limit 20
API And Automation
Use gh api when subcommands do not expose required fields.
gh api repos/:owner/:repo/pulls --method POST -f title='My PR' -f head='feature-branch' -f base='main'
Prefer machine-readable output for automation:
- Use
--jsonwhere available - Use
gh apioutput withjqfor deterministic extraction of fields likenumber,title,body, andurl
URL Handling
When the user provides a GitHub URL, parse owner/repo/number and fetch details with gh commands instead of browser scraping.
Examples:
- PR URL ->
gh pr view <number> --repo <owner>/<repo> ... - Issue URL ->
gh issue view <number> --repo <owner>/<repo> ...
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 · 118 lines · 51 tokens per session scan A 5e1c97386ad4
gh is a skill published in the GitHub repository adampoit/ai (2 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 738 once invoked, about $0.0002 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
openspec-bulk-apply-change
Use when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.
openspec-git-discipline
Use when running OpenSpec propose, continue, apply, verify, archive, or worktree workflows where proposal artifacts, branches, merges, or archive timing affect git history.
release
Verify, write the CHANGELOG, cut a version — then hand the release sequence back.
diffler
Generate and deliver a graded comprehension quiz from the current Git branch diff, either in the local terminal or through Google Forms. Use when a user asks to prove, test, or verify understanding of branch changes, a feature branch, or a pull request.
deploy-automation
Workflows and best practices for CI/CD automation, deployment strategies, and production releases. Use when implementing or improving deployment pipelines, managing environments, or planning production releases.
wrap-phase
Wraps up a development phase by cleaning AGENTSYNC.md, summarizing work, and committing changes.