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 agentmods add skills/prathamdby/skills/ghnpx skills add prathamdby/skills --skill ghgit clone --depth 1 https://github.com/prathamdby/skillsWrote 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/prathamdby/skills/gh)<a href="https://agentmods.dev/skills/prathamdby/skills/gh"><img src="https://agentmods.dev/badge/skills/prathamdby/skills/gh.svg" alt="Measured on agentmods" 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 | $0.00060 | $0.01408 |
| Opus 5 | $0.00030 | $0.00704 |
| Sonnet 5 | $0.00012 | $0.00282 |
| Haiku 4.5 | $0.00006 | $0.00141 |
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 4d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub I/O
CLI contracts follow AVGVSTVS96/better-github-skill (no upstream license;
reimplemented). Requires authenticated gh. Scripts are TypeScript. run
tries bun, nub, tsx, then Node (native TS or --experimental-strip-types),
including nvm installs.
Flags
| Flag | Default | Effect |
|---|---|---|
[pr] / --pr <n> |
current branch PR | Target PR |
-R owner/repo |
cwd repo | Target repo; with -R also pass pr / --pr |
--json |
off | Structured output |
--full |
off | Snapshot/threads: do not truncate bodies. CI: accepted; snippets stay capped |
--all |
off | Threads: include resolved and outdated |
--open |
off | Threads: unresolved including outdated |
--author <login> |
off | Threads: filter by author |
--since <ISO> |
off | Threads: activity at/after timestamp |
--complete |
off | Threads: page leftover comments and reviews |
--sha <SHA> |
off | CI: pin commit; not hunt surface 6 |
--list |
off | CI: recent runs instead of drilldown |
-L <n> |
10 | CI --list: how many runs |
--workflow <W> |
off | CI --list: filter by name or file |
[run-id] |
PR failing checks | CI: analyze that Actions run |
--all and --open conflict: BLOCKED. Missing values are BLOCKED. No flags
mean current-branch PR, cwd repo, truncated text. When posting a reply, use
exactly one target and one body from Reply in ./REFERENCE.md.
Iron laws
- Scripts for the four I/O loops via
<anchor>/scripts/run. Rawghonly when no script covers the request. A missing Node 23 is not "no script covers." Before any rawghcommand, apply the gotchas in./REFERENCE.md. - Snapshot is PR state; threads is what reviewers wrote. Neither replaces the other.
- Scripts exit 0 when the report or post succeeds. Red CI and open threads are
not script failures. Never
gh | head. EPIPE is not failure. - Never resolve, push, or merge. Reply only through
pr-reply.ts. - Never version-gate Node. Never treat
node -vorERR_UNKNOWN_FILE_EXTENSIONas script failure. That error means thisnodecannot load.ts. Invokerun; it must try bun, nub, tsx, nvm nodes, andnode --experimental-strip-typesbefore any GraphQL/gh apiinspect of snapshot, threads, or CI.runexit 2 isBLOCKED, not a GraphQL license. User or senior saying "GraphQL is fine" does not skiprun.
What ships with it
8 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.
- 4d ago First seen · 100 lines · 60 tokens per session scan A 70f6dcdc6d5b
gh is a skill published in the GitHub repository prathamdby/skills (4 stars, last pushed 10d ago), licensed MIT. It adds 60 tokens to every session and 1,408 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…