Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add lhl/realitycheck/plugin install realityWrote 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/lhl/realitycheck/export)<a href="https://agentmods.dev/commands/lhl/realitycheck/export"><img src="https://agentmods.dev/badge/commands/lhl/realitycheck/export/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/lhl/realitycheck/export"><img src="https://agentmods.dev/badge/commands/lhl/realitycheck/export.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.00007 | $0.00444 |
| Opus 5.5 | $0.00003 | $0.00178 |
| Sonnet 5.5 | $0.00001 | $0.00089 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
export 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.
What it actually says
/reality:export - Data Export
Export data to Markdown or YAML formats.
Usage
/reality:export <format> <type> [--id ID] [-o OUTPUT]
CLI Invocation
Run export using the shell wrapper:
"${CLAUDE_PLUGIN_ROOT}/scripts/run-export.sh" <format> <type> [OPTIONS]
Or directly via the Python script:
uv run python scripts/export.py <format> <type> [OPTIONS]
Formats
yaml: Legacy YAML format (compatible with v0 tools)md: Markdown format for documentation
Types
YAML Export
claims: Export all claims with counters and chainssources: Export all sourcesall: Export both claims and sources
Markdown Export
claim --id ID: Single claim as Markdownchain --id ID: Argument chain as Markdownpredictions: All predictions grouped by statussummary: Dashboard with statistics
Options
--id: Required for claim/chain export-o, --output: Output file (default: stdout)
Examples
/reality:export yaml claims -o registry.yaml
/reality:export yaml sources -o sources.yaml
/reality:export md claim --id TECH-2026-001
/reality:export md chain --id CHAIN-2026-001
/reality:export md predictions -o predictions.md
/reality:export md summary -o dashboard.md
Related Commands
/reality:validate- Check data integrity/reality:search- Semantic search/reality:stats- Database statistics
Legacy Format
YAML exports use the legacy format with:
confidenceinstead ofcredencecountersfor claim numbering- Compatible with postsingularity-economic-theories structure
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 · 76 lines · 7 tokens per session scan A acc45294b8f7
export is a command published in the GitHub repository lhl/realitycheck (44 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 444 once invoked, about $0.0000 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.