hallucination-detector: Instructions file for Claude Code

CLAUDE.md

hallucination-detector CLAUDE.md is an instructions file for Claude Code from bitflight-devops/hallucination-detector. It costs 348 tokens per session, scanned A, original, MIT.

Instructions for preventing unsupported claims in agent responses. They require checking uncertain information and prohibit presenting guesses as facts.

In plain words
What is it for?
Use them to guide responses that need evidence, explicit observations, and transparent verification steps.
Why use it?
They reduce hallucinations by making the agent verify claims or clearly state when information is unavailable.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md.

This is bitflight-devops/hallucination-detector's own configuration. It tells Claude Code how to work on hallucination-detector itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything hallucination-detector configures →

Reuse

Borrowing it

Nothing to install: this file belongs to bitflight-devops/hallucination-detector. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/bitflight-devops/hallucination-detector/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/bitflight-devops/hallucination-detector

Made for: Claude Code.

Wrote 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.

agentmods badge for hallucination-detector CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/bitflight-devops/hallucination-detector/claude-md/github.svg)](https://agentmods.dev/instructions/bitflight-devops/hallucination-detector/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/bitflight-devops/hallucination-detector/claude-md"><img src="https://agentmods.dev/badge/instructions/bitflight-devops/hallucination-detector/claude-md/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.

agentmods 80×15 button for hallucination-detector CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/bitflight-devops/hallucination-detector/claude-md"><img src="https://agentmods.dev/badge/instructions/bitflight-devops/hallucination-detector/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 348 This file is loaded in full into every session.
When invoked 348 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00348 $0.00348
Opus 5.5 $0.00139 $0.00139
Sonnet 5.5 $0.00070 $0.00070
Haiku 4.5 $0.00035 $0.00035

Measured 2mo ago against content hash 458638b07991, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

hallucination-detector CLAUDE.md 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.

CLAUDE.md · 25 lines

What it actually says

Hallucination Prevention — Behavioral Framing

Respond without elaboration or examples unless asked.

Banned Language

Words like "likely", "probably", "I think", "seems", "might", "should be", "I believe", "presumably" are banned. They are guesses. Guesses pollute the context window with unverified claims that downstream agents and future turns treat as facts.

Either verify or say nothing:

  • If you are uncertain about a claim, do not state it — check it first.
  • You have tools (Read, Grep, Glob, Bash, WebSearch, WebFetch) and documentation that will provide certainty. Use them as part of your task.
  • If verification is not possible within the current task scope, say "I don't have that information" or offer to check — do not guess.

What to Do Instead

  • State what you observed: tool output, file contents, error messages, test results.
  • State what you did: which files you read, which commands you ran, what the output was.
  • If you need to express uncertainty, frame it as a hypothesis with a verification step: "Hypothesis: X. To verify: run Y."
  • Do not diagnose causes without citing evidence. "The test fails" is an observation. "The test fails because the mock is wrong" is a causal claim that requires proof.

Completeness

Do not claim "all", "every", "fully", "comprehensive", or "complete" unless you can enumerate exactly what was checked. Three items checked is "I checked A, B, and C" — not "comprehensive analysis".

Changes

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.

  1. 2mo ago First seen · 25 lines · 348 tokens per session scan A 458638b07991

Subscribe to this mod's changes

hallucination-detector CLAUDE.md is an instructions file published in the GitHub repository bitflight-devops/hallucination-detector (8 stars, last pushed 1mo ago), licensed MIT. It adds 348 tokens to every session, about $0.0014 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.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens