A command that packages a saved NeatContext context into a folder for sharing or moving to another machine.

Use it to export a named or connected context to a chosen destination folder, then bring it back with the matching import command.

It provides a self-contained copy that a teammate can import instead of transferring context files individually.

export — Command by XTSoftwareLabs

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/xtsoftwarelabs/neatcontext-plugins/export

Clone the repo

git clone --depth 1 https://github.com/XTSoftwareLabs/neatcontext-plugins

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 420 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.

Model	Per session	Once invoked
Fable 5	$0.00011	$0.00420
Opus 5	$0.00005	$0.00210
Sonnet 5	$0.00002	$0.00084
Haiku 4.5	$0.00001	$0.00042

Measured 2d ago against content hash 8842ce55cbcd, 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.

plugins/claude-code/neatcontext/commands/export.md · 44 lines

What it actually says

Export a context saved from a conversation into a self-contained bundle folder, so it can be copied to another machine or handed to a teammate and brought back in with /neatcontext:import.

Your contexts:

!node "${CLAUDE_PLUGIN_ROOT}/src/claude/neatcontext-cli.mjs" list

The user asked to export: $ARGUMENTS

Work out which context and which destination folder they mean:

The destination is the folder the bundle is written into. A subfolder named after the context is created there, so one folder can hold several exports.
If no destination was given, ask for it and stop.
If no context was named, the connected one is used. If none is connected, show the list above and ask which one they mean. Do not guess.

Then run, passing each value as its own quoted argument:

node "${CLAUDE_PLUGIN_ROOT}/src/claude/neatcontext-cli.mjs" export "<name>" --to "<destination folder>"

Relay the result. Points to cover when they come up:

A context made by /neatcontext:create cannot be exported. It links a folder the plugin does not own, so there is nothing self-contained to hand over. The command says so; relay that they should copy that folder across themselves and re-create the context on the other machine.
If the destination already holds a bundle for this context, the command refuses. Confirm with the user that replacing it is what they want, then rerun the same command with --force.
The exported bundle is a copy. The context in this session is unchanged and stays connected.

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.

2d ago First seen · 44 lines · 11 tokens per session scan A 8842ce55cbcd

Subscribe to this mod's changes

export is a command published in the GitHub repository XTSoftwareLabs/neatcontext-plugins (13 stars, last pushed 9d ago), licensed MIT. It adds 11 tokens to every session and 420 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-30.

ai-context claude-code claude-code-plugin claude-code-skills claude-plugin claude-skills

export

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

bug

feature

qa

telemetry

ci

docs