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 tomzx/agents --skill ghxgit clone --depth 1 https://github.com/tomzx/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/tomzx/agents/ghx)<a href="https://agentmods.dev/skills/tomzx/agents/ghx"><img src="https://agentmods.dev/badge/skills/tomzx/agents/ghx.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00124 | $0.02349 |
| Opus 5 | $0.00062 | $0.01175 |
| Sonnet 5 | $0.00025 | $0.00470 |
| Haiku 4.5 | $0.00012 | $0.00235 |
Grade A, and why
ghx 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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ghx Skill
ghx is an extended GitHub CLI. It talks to the GitHub GraphQL API directly to
provide two kinds of capability:
- Cached browsing — fetches issues, pull requests, and their comments and
caches every result to
~/.cache/ghx/cache/<host>/<owner>/<repo>to minimise API calls. - Comment operations — inline review comments, line-range comments, thread
replies, pending reviews, and a local "stash" for offline review comments,
none of which the standard
ghCLI supports.
Prerequisites
Binary
Check whether the binary is on PATH; install from the latest release if not:
if ! command -v ghx &>/dev/null; then
go install github.com/tomzxcode/ghx@main
fi
Pre-built binaries are also available at https://github.com/TomzxCode/ghx/releases/tag/latest.
Authentication
ghx reads GH_TOKEN or GITHUB_TOKEN from the environment, and falls back
to gh auth token (GitHub CLI). Set the token if neither is available:
export GH_TOKEN=<token>
Target repository
All commands accept --repo [HOST/]OWNER/REPO (or -R). When omitted, the repo
is auto-detected from the origin remote of the current directory. Confirm the
target before running expensive or write operations:
git remote get-url origin
Cached browsing
Pre-populate the cache
Run cache once to pull everything down so subsequent list/view commands are
served instantly from disk:
ghx cache # default: stale after 60 min
ghx cache --repo owner/repo
ghx cache --cache-duration 120 # stale after 2 hours
ghx cache --cache-duration 0 # always re-fetch (delta)
ghx cache --force # force full re-fetch
List issues
ghx issue list # open issues (default)
ghx issue list --state all
ghx issue list --author alice
ghx issue list --assignee bob
ghx issue list --label bug
ghx issue list --label bug --label p1 # AND logic
ghx issue list --milestone v2.0
ghx issue list --search "memory leak"
ghx issue list --limit 50
ghx issue list --json # machine-readable output
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 · 308 lines · 124 tokens per session scan A cb2bec0fa51a
ghx is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed 4d ago), licensed MIT. It adds 124 tokens to every session and 2,349 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.