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 commands/bitflight-devops/hallucination-detector/start-issueWrote 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/commands/bitflight-devops/hallucination-detector/start-issue)<a href="https://agentmods.dev/commands/bitflight-devops/hallucination-detector/start-issue"><img src="https://agentmods.dev/badge/commands/bitflight-devops/hallucination-detector/start-issue/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/commands/bitflight-devops/hallucination-detector/start-issue"><img src="https://agentmods.dev/badge/commands/bitflight-devops/hallucination-detector/start-issue.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.00000 | $0.00910 |
| Opus 5.5 | $0.00000 | $0.00364 |
| Sonnet 5.5 | $0.00000 | $0.00182 |
| Haiku 4.5 | $0.00000 | $0.00091 |
Grade A, and why
start-issue 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start Work on Issue
You are beginning work on GitHub issue $ARGUMENTS.
Follow these steps in order. Do not skip steps. Do not jump to implementation.
Step 1: Load the issue
node .claude/scripts/gh-api.cjs issue view $ARGUMENTS
Read the full issue body, labels, milestone, and assignee. Extract:
- Title and summary
- Impact type label (e.g.
impact: additive) - Risk level label (e.g.
risk: low) - Phase label (e.g.
phase: 1-additive-patterns) - Acceptance criteria from the issue body
If no acceptance criteria exist in the body, state that and ask the user whether to proceed or define criteria first.
Step 2: Load deep analysis and comments
node .claude/scripts/gh-api.cjs issue comment search $ARGUMENTS \
--section "Deep Analysis: Implementation Impact"
If found, extract:
- Dependencies (blocked by / blocks)
- Files touched
- Failure modes
- Contract impact
If no deep analysis comment exists, proceed using the issue body alone. If a blocking dependency is listed and still open, warn the user before proceeding.
Step 3: Determine workflow weight
Based on the labels extracted in Step 1:
- Lightweight (phase 1 + risk low + impact additive): Skip the research substep in Step 5. Go straight from understanding to objectives.
- Standard (everything else): Follow all substeps in Step 5.
Step 4: Create a feature branch
Derive a branch name from the issue number and title:
- Format:
feat/<issue-number>-<kebab-case-slug>(max 50 chars for the slug) - Example: issue #15 "Cognitive bias detection" →
feat/15-cognitive-bias-detection
Check if the branch exists first:
git branch --list "feat/$ARGUMENTS-*"
If it exists, check it out. Otherwise create it:
git checkout -b <branch-name>
Step 5: Plan the work
Follow the Working Process defined in .claude/CLAUDE.md § "Working Process" (steps 1–4: understand, research, objectives, gap analysis). If this is a lightweight issue (Step 3), skip the research substep.
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 · 132 lines · 0 tokens per session scan A ce7baae49a80
start-issue is a command published in the GitHub repository bitflight-devops/hallucination-detector (8 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 910 tokens. 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 commands, from other repositories
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
run-tasks
Execute GitHub issues using full EPCT workflow (Explore-Plan-Code-Test). Converts issue requirements into completed PR.
sync-github
Ejecuta SonIA Sync: refleja el tablero local en GitHub Issues usando gh CLI.
flow
Universal workflow entry point. Use /flow for skill-driven GitHub development. Verbs: start, commit, pr, review, address, merge, resolve, release, status, learn, setup, explain, debug, design, brainstorm, issue.
ship
Prepare the current branch to ship, commit messages, semver bump, and a PR description, all for approval.
hotfix
Emergency fix workflow that bypasses normal sprint processes with a full audit trail. Creates hotfix branch, tracks approvals, and ensures the fix is backported correctly.