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 Hmbown/Wizards-of-the-Ghosts --skill zone-of-truthgit clone --depth 1 https://github.com/Hmbown/Wizards-of-the-GhostsWrote 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/hmbown/wizards-of-the-ghosts/zone-of-truth)<a href="https://agentmods.dev/skills/hmbown/wizards-of-the-ghosts/zone-of-truth"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/zone-of-truth/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/hmbown/wizards-of-the-ghosts/zone-of-truth"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/zone-of-truth.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.00031 | $0.00683 |
| Opus 5 | $0.00015 | $0.00342 |
| Sonnet 5 | $0.00006 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
zone-of-truth 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 9d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zone of Truth
Establish a high-integrity epistemic environment where claims must be sourced and uncertainty labeled.
What This Skill Does
Enter a mode where every assertion is backed by evidence, confidence is calibrated, speculation is flagged, and hallucination is actively resisted. In this grimoire, Zone of Truth is treated as a metaphorical spell with a shipping-now delivery profile. Canonical reference input: Zone of Truth (spell).
When To Use
- Use $zone-of-truth ACTIVATED to signal the zone is active
- Include the custom phrase: "Switching into high-integrity mode: source every claim, label every uncertainty, flag anything speculative"
- High-stakes decisions requiring maximum epistemic rigor
- Conversation has drifted into speculation and needs reset to verified ground
- Need to clearly separate what is known, inferred, and guessed
- Roadmap debates, compliance verification, vendor claims, customer demand validation
Prerequisites
- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.
Procedure
- Restate the target, the success condition, and any no-touch boundaries before taking action.
- Activate truth-zone discipline: all claims require sources or explicit confidence labels.
- Re-examine any prior assertions in the conversation and flag unsupported ones.
- For each new claim, provide the evidence basis or clearly mark it as inference, estimation, or speculation.
- Maintain the zone until the user explicitly dismisses it or the conversation ends.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- A conversation mode where every claim is sourced or confidence-labeled.
- A re-audit of prior unsupported assertions if the zone is activated mid-conversation.
- Clear visual markers distinguishing fact, inference, and speculation.
Pitfalls / Guardrails
- Keep the metaphor anchored to a real mechanism instead of drifting into lore.
- Error disclaimer: "This zone does not eliminate all error — it reduces unsourced assertions, not all mistakes."
- Normal mode defense: "Normal mode is not dishonest — this is about rigor, not trustworthiness."
- Absence of evidence caveat: "Absence of evidence ≠ evidence of absence — limited findings reflect documentation gaps, not necessarily reality."
- Include a two-part boundary:
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.
- 9d ago First seen · 72 lines · 31 tokens per session scan A 02450084a492
zone-of-truth is a skill published in the GitHub repository Hmbown/Wizards-of-the-Ghosts (107 stars, last pushed 5mo ago), licensed CC0-1.0. It adds 31 tokens to every session and 683 once invoked, about $0.0002 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
agent-creator
Meta-agent for creating new custom agents, skills, and MCP integrations. Expert in agent design, MCP development, skill architecture, and rapid prototyping. Activate on 'create agent', 'new skill', 'MCP server', 'custom tool', 'agent design'. NOT for using existing agents (invoke them directly), general coding (use…
code-research
Use when produce structured understanding of unfamiliar codebases — architecture, data flows, dependencies, and conventions. Use when joining a new project, tracing feature implementations, or mapping system architecture.
crewai-agents
Use when crewAI multi-agent orchestration — agents, tasks, crews, tools, memory, delegation. Use when working with crewai agents.
code-agent
Use when implementing features from specs — reads requirements, writes code with tests, iterates until verification passes.
deploy-agent
Use when ship code through controlled pipeline with verification gates and rollback plans.
planning-agent
Use when decompose complex tasks into executable steps with dependencies, risk assessment, and verification criteria.