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 agentmods add commands/dropfan/claude-code-plugins/raw-exportgit clone --depth 1 https://github.com/DropFan/claude-code-pluginsWhat 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 | $0.00010 | $0.01205 |
| Opus 5 | $0.00005 | $0.00602 |
| Sonnet 5 | $0.00002 | $0.00241 |
| Haiku 4.5 | $0.00001 | $0.00120 |
Grade A, and why
raw-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 yesterday.
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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Working directory: !
pwd - Current date: !
date '+%Y-%m-%d %H:%M' - Plugin root: ${CLAUDE_PLUGIN_ROOT}
Task
Export raw conversation data directly from Claude Code's JSONL session files. Unlike /save-chat which reconstructs content from memory, this command reads the original data files, ensuring complete and faithful export.
User arguments: $ARGUMENTS
Step 0: Load Settings
Load settings from .claude/chat-saver.local.md following ${CLAUDE_PLUGIN_ROOT}/skills/conversation-export/references/settings-loading.md. Extract: save_dir, default_format, custom_footer.
Step 1: Parse Arguments
Parse the optional arguments from $ARGUMENTS:
- --format —
md(default),jsonl,json, orhtml - --full — Include all record types (progress, file-history-snapshot, etc.), not just user/assistant messages
- --list — List available sessions and let user pick one
- --session — Specify a session ID (supports UUID prefix match)
If $ARGUMENTS is empty, use defaults (format from settings or md, latest session).
If arguments are ambiguous or invalid, use AskUserQuestion to let the user choose:
For format:
md— Markdown with YAML frontmatter,## User/## Assistantstructurehtml— Styled HTML, viewable in browserjsonl— Filtered JSONL, machine-readablejson— JSON array, machine-readable
Step 2: Locate Project Data Directory
- Get the current working directory:
pwd
- Encode the path to match Claude Code's directory naming:
echo "$CWD" | sed 's|^/||' | sed 's|/|-|g'
The encoding removes the leading / then replaces all / with -.
- Construct the project data path:
~/.claude/projects/-<encoded-path>/
- Verify the directory exists:
ls ~/.claude/projects/<encoded-path>/*.jsonl 2>/dev/null | head -1
If the directory doesn't exist or contains no JSONL files, inform the user and stop.
Step 3: Session Selection
If --list is specified:
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.
- yesterday First seen · 144 lines · 10 tokens per session scan A 66db5c9cf2f2
raw-export is a command published in the GitHub repository DropFan/claude-code-plugins (7 stars, last pushed 26d ago), licensed MIT. It adds 10 tokens to every session and 1,205 once invoked, about $0.0001 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-31.
Other commands, from other repositories
prompt
System instructions for writing effective prompts. Apply when generating commands, skills, agents, or any LLM instructions.
full
Run the full hope pipeline — intent, shape, target, freeze as needed — then execute.
status
Show tlive daemon, channel, and Codex companion status.
csv-to-numbers
Convert a CSV into a formatted Numbers workbook.
rust-critique
Deep code critique — read the target Rust code and apply the full review process. Evaluates soundness, ownership, error handling, type design, async correctness, performance, and architecture. Think like a senior Rust engineer giving honest feedback.
dotnet-structure
Analyze and recommend .NET backend solution and folder structure improvements. Checks projects, layers, oversized files, and boundary clarity.