Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/bitflight-devops/hallucination-detectornpx agentmods add skills/bitflight-devops/hallucination-detector/ghWrote 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/bitflight-devops/hallucination-detector/gh)<a href="https://agentmods.dev/skills/bitflight-devops/hallucination-detector/gh"><img src="https://agentmods.dev/badge/skills/bitflight-devops/hallucination-detector/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/bitflight-devops/hallucination-detector/gh"><img src="https://agentmods.dev/badge/skills/bitflight-devops/hallucination-detector/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.00049 | $0.01859 |
| Opus 5.5 | $0.00020 | $0.00744 |
| Sonnet 5.5 | $0.00010 | $0.00372 |
| Haiku 4.5 | $0.00005 | $0.00186 |
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 2mo 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub API — Setup and Usage
Purpose
Provides programmatic GitHub API access for the hallucination-detector repo using octokit (full SDK) with automatic proxy support. All operations use Node.js scripts — no gh CLI binary is needed.
When to Use
- Need to interact with GitHub API (issues, PRs, labels, milestones)
- Creating or listing pull requests
- Reviewing PRs: list/view/submit/dismiss reviews, code annotation comments
- Managing CI: list/view/rerun workflow runs, check run annotations and logs
- Managing GitHub Issues, Projects V2, or Labels
- Running in a proxy environment where direct DNS to
api.github.comis unavailable
Authentication
GITHUB_TOKEN environment variable provides authentication. All scripts read it automatically via createGitHubClient().
const { createGitHubClient, OWNER, REPO } = require('./.claude/scripts/lib/github-client.cjs');
const octokit = createGitHubClient();
The client auto-detects HTTPS_PROXY / HTTP_PROXY env vars and routes requests through the egress proxy via undici.ProxyAgent. No manual proxy configuration needed.
Scripts
General-purpose GitHub API — gh-api.cjs
# Issues
node .claude/scripts/gh-api.cjs issue list
node .claude/scripts/gh-api.cjs issue create --title "feat: add X" --label "type:feature" --label "priority:p1"
node .claude/scripts/gh-api.cjs issue view 42
node .claude/scripts/gh-api.cjs issue comment 42 --body "Implemented in PR #45."
node .claude/scripts/gh-api.cjs issue comment list 27 [--user "coderabbitai[bot]"]
node .claude/scripts/gh-api.cjs issue comment view 123456
node .claude/scripts/gh-api.cjs issue comment search 27 --user "coderabbitai[bot]" --section "Prompt for AI Agents" --source reviews
# Pull Requests
node .claude/scripts/gh-api.cjs pr list
node .claude/scripts/gh-api.cjs pr create --title "feat: add X" --base main --body "Details"
# Labels
node .claude/scripts/gh-api.cjs label list
node .claude/scripts/gh-api.cjs label create --name "priority:p0" --color "D73A4A" --description "Critical"
# PR Reviews
node .claude/scripts/gh-api.cjs review list 27
node .claude/scripts/gh-api.cjs review view 27 123456
node .claude/scripts/gh-api.cjs review submit 27 --event APPROVE --body "LGTM"
node .claude/scripts/gh-api.cjs review dismiss 27 123456 --message "Outdated"
# Code Annotation Comments (PR review comments)
node .claude/scripts/gh-api.cjs review-comment list 27
node .claude/scripts/gh-api.cjs review-comment view 123456
node .claude/scripts/gh-api.cjs review-comment reply 27 123456 --body "Fixed"
# CI Check Runs (accepts PR number or git ref/SHA)
node .claude/scripts/gh-api.cjs checks list 27
node .claude/scripts/gh-api.cjs checks list main
node .claude/scripts/gh-api.cjs checks view 123456
node .claude/scripts/gh-api.cjs checks annotations 123456
# Workflow Runs
node .claude/scripts/gh-api.cjs run list [--limit 10] [--status completed]
node .claude/scripts/gh-api.cjs run view 123456
node .claude/scripts/gh-api.cjs run rerun 123456 [--failed-only]
node .claude/scripts/gh-api.cjs run logs 123456
node .claude/scripts/gh-api.cjs run cancel 123456
What ships with it
5 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.
- 2mo ago First seen · 182 lines · 49 tokens per session scan A 9e3d91c9564d
gh is a skill published in the GitHub repository bitflight-devops/hallucination-detector (8 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 1,859 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
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
backlog
Read, work, and maintain a Git repo's deferred-work items in docs/backlog/, one file per item. Use when the user says "backlog", "check backlog", "what's on my backlog", "work the backlog", "address the backlog", "add to backlog", "clean up backlog", or when a review or task produced items that are real but not being…
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
glab
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
jira
Jira integration — view issues, generate branches, create tickets, transition status. Use when: user mentions Jira ticket key (XX-123), says /jira, wants to create branch from ticket, create a new ticket, or update Jira status. Not for: GitHub issues (use issue-analyze).
apex-status
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.