agentmods.dev

export

A command that exports stored research data as Markdown or YAML files. The data can include claims, sources, argument chains, predictions, or summary information.

In plain words
What is it for?
Creating claim or argument-chain documents, exporting source and claim registries, and generating prediction or dashboard summaries.
Why use it?
It avoids manually copying records into documentation or other tools and supports formats suited to different workflows.

Command

41 2mo ago A scan 7 tokens original Apache-2.0
View the source file lhl/realitycheck
Install

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.

agentmods
npx agentmods add commands/lhl/realitycheck/export
Clone the repo
git clone --depth 1 https://github.com/lhl/realitycheck
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 444 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00007 $0.00444
Opus 5 $0.00003 $0.00222
Sonnet 5 $0.00001 $0.00089
Haiku 4.5 $0.00001 $0.00044

Measured 2d ago against content hash acc45294b8f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

integrations/claude/plugin/commands/export.md · 76 lines

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 chains
  • sources: Export all sources
  • all: Export both claims and sources

Markdown Export

  • claim --id ID: Single claim as Markdown
  • chain --id ID: Argument chain as Markdown
  • predictions: All predictions grouped by status
  • summary: 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
  • /reality:validate - Check data integrity
  • /reality:search - Semantic search
  • /reality:stats - Database statistics

Legacy Format

YAML exports use the legacy format with:

  • confidence instead of credence
  • counters for claim numbering
  • Compatible with postsingularity-economic-theories structure
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. 2d ago First seen · 76 lines · 7 tokens per session scan A acc45294b8f7

Subscribe to this mod's changes

export is a command published in the GitHub repository lhl/realitycheck (41 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 444 once invoked, about $0.0000 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-08-30.

Analytics and metricsResearchagentanalysis
Related

Other commands, from other repositories

MIGRATE_DESIGN

Design doc for the migration tool PR. Author: Sol ([email protected]). Co-authored-by: wakesync.

elizaOS/eliza · 0 tokens

awesome-chatgpt

Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.

taishi-i/awesome-ChatGPT-repositories · 0 tokens

agentlas-cloud

Staff a task only from the signed-in owner's Agent Cloud agents.

agentlas-ai/Agentlas-OS · 13 tokens

commit

智能生成 Git 提交信息并提交.

echoVic/blade-code · 8 tokens

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

hamr0/agentic-toolkit · 35 tokens

create-issue

Transform feature descriptions, bug reports, or improvement ideas into well-structured GitHub issues.

opsmill/infrahub-mcp · 18 tokens