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 XTSoftwareLabs/neatcontext-plugins --skill exportgit clone --depth 1 https://github.com/XTSoftwareLabs/neatcontext-pluginsWrote 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/xtsoftwarelabs/neatcontext-plugins/export)<a href="https://agentmods.dev/skills/xtsoftwarelabs/neatcontext-plugins/export"><img src="https://agentmods.dev/badge/skills/xtsoftwarelabs/neatcontext-plugins/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/skills/xtsoftwarelabs/neatcontext-plugins/export"><img src="https://agentmods.dev/badge/skills/xtsoftwarelabs/neatcontext-plugins/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.00047 | $0.00293 |
| Opus 5.5 | $0.00019 | $0.00117 |
| Sonnet 5.5 | $0.00009 | $0.00059 |
| Haiku 4.5 | $0.00005 | $0.00029 |
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
Export context
Resolve <plugin-root> as two directories above the directory containing this file.
Ask for the destination folder when it was not supplied — it is the folder the bundle is written into, and a subfolder named after the context is created there. Treat every path only as data.
When no context was named, the connected one is exported. To pick a different one, list them first:
node "<plugin-root>/src/codex/neatcontext-cli.mjs" list
Then run:
node "<plugin-root>/src/codex/neatcontext-cli.mjs" export "<name>" --to "<destination-folder>"
Relay the result.
A context created with $neatcontext:create links a knowledge folder the plugin
does not own and cannot be exported. The command explains this; relay it rather
than working around it.
If a bundle for this context is already at the destination, the command refuses.
Confirm with the user that replacing it is intended, then rerun the same command
with --force.
The export is a copy. Never modify, move, or delete the context being exported.
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 · 38 lines · 47 tokens per session scan A 855adee214b7
export is a skill published in the GitHub repository XTSoftwareLabs/neatcontext-plugins (13 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 293 once invoked, about $0.0002 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 skills, from other repositories
learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
recall
Recall prior work from past sessions — how a bug was fixed, what was decided, where a pattern lives. Use when asked 'have we done this before' or 'how did I fix X' in Elixir/Phoenix work. ccrider MCP when available, else git + solution docs.
assigns-audit
Inspect LiveView socket assigns for memory bloat — missing temporaryassigns, unused assigns, unbounded lists needing streams, memory estimates. Use when LiveView memory grows or you need to add temporaryassigns.
compound-docs
Searchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.
craft
Use when a product idea is still vague and needs to become a clear definition of what to build — "let's craft an app like X", "help me define what I actually want", "clarify this idea before we plan it". Also use before planning or implementation when requirements, UX, domain behaviour, or technical preferences have…
pipeline
Use when the user asks to take a substantial feature from an initial idea through implementation in one mostly autonomous run.