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/xtsoftwarelabs/neatcontext-plugins/listgit clone --depth 1 https://github.com/XTSoftwareLabs/neatcontext-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.00009 | $0.00168 |
| Opus 5 | $0.00005 | $0.00084 |
| Sonnet 5 | $0.00002 | $0.00034 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
list 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.
What it actually says
List the contexts stored locally by the plugin.
!node "${CLAUDE_PLUGIN_ROOT}/src/claude/neatcontext-cli.mjs" list
Relay the output above verbatim — it is already the answer. Do not re-format it,
summarize it, or expand on any (none — ...) note; those
lines say everything that needs saying. Then one closing line: connect one with
/neatcontext:use <name>, or — only when the list is empty — create one with
/neatcontext:create or save this conversation with
/neatcontext:save.
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 · 16 lines · 9 tokens per session scan A 93b212c8765a
list is a command published in the GitHub repository XTSoftwareLabs/neatcontext-plugins (13 stars, last pushed 9d ago), licensed MIT. It adds 9 tokens to every session and 168 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.
Other commands, from other repositories
bug
Reproduce then TDD-fix a ready-for-agent bug ticket in this checkout. Web bugs get a browser repro first.
feature
Implement a ready-for-agent feature ticket in this checkout. Do not expand the ask.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.
telemetry
Pull breakage or product-performance evidence. Funnels, feature completion, errors. Do not implement.
ci
Watch gh pr checks until green and fix failures on this branch. Do not merge.
docs
Docs-only change for a ready-for-agent ticket. No application code.