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/statusgit 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.00248 |
| Opus 5 | $0.00005 | $0.00124 |
| Sonnet 5 | $0.00002 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
status 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
Report the current connection.
!node "${CLAUDE_PLUGIN_ROOT}/src/claude/neatcontext-cli.mjs" status
Relay the status above to the user, keeping it short. If no context is connected,
mention they can connect one with /neatcontext:use. If it reports a problem
with a context — its files or its knowledge folder gone — relay that too,
along with what to do about it.
If it says the routing description was derived from an older version of the
profile, offer to refresh it: read the profile, write a fresh one-line scope
description the same way /neatcontext:use does, and record it with
neatcontext-cli.mjs describe "<name>" --use-when "<line>".
Keep /neatcontext:create and /neatcontext:save distinct when suggesting a
next step: create starts a fresh context from user answers; save distills useful
work already in the current conversation into a new or existing context.
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 · 23 lines · 10 tokens per session scan A 1708fdc4b129
status 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 248 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.