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/modegit 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.00010 | $0.00250 |
| Opus 5 | $0.00005 | $0.00125 |
| Sonnet 5 | $0.00002 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
mode 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.
What it actually says
Set or show how this session routes itself between contexts.
The user supplied:
$ARGUMENTS
Accept only no argument, one of auto, ask, or manual, and an optional
trailing --global. If anything else was supplied, do not run it as shell
input; show the accepted form instead.
Run the bundled CLI with the validated literal mode:
node "${CLAUDE_PLUGIN_ROOT}/src/claude/neatcontext-cli.mjs" mode <mode> [--global]
Omit <mode> [--global] when the user supplied no argument. Relay the output
as it is. Do not explain the modes again if the command already listed them,
and do not switch context as part of running this command.
The mode set here applies to this session only.
/neatcontext:mode <mode> --global changes the default for new sessions
instead.
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 · 31 lines · 10 tokens per session scan A 409ede0f9068
mode is a command published in the GitHub repository XTSoftwareLabs/neatcontext-plugins (13 stars, last pushed 9d ago), licensed MIT. It adds 10 tokens to every session and 250 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.
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.