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 extensionsgit 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/extensions)<a href="https://agentmods.dev/skills/xtsoftwarelabs/neatcontext-plugins/extensions"><img src="https://agentmods.dev/badge/skills/xtsoftwarelabs/neatcontext-plugins/extensions/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/extensions"><img src="https://agentmods.dev/badge/skills/xtsoftwarelabs/neatcontext-plugins/extensions.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.00045 | $0.00423 |
| Opus 5.5 | $0.00018 | $0.00169 |
| Sonnet 5.5 | $0.00009 | $0.00085 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
extensions 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
Context extensions
Resolve <plugin-root> as two directories above the directory containing this file. Run:
node "<plugin-root>/src/codex/neatcontext-cli.mjs" extensions
Relay the report. Two separate things are being reported, and the difference matters:
- What the context expects — the extension it declares and the capability that provides. This travels with the context and is the same on every machine it reaches.
- What this machine provides for it. That is local, hand-written, and lives in the bindings file the report names. Nothing configures it automatically, and nothing inside a shared context can configure it.
If something is reported as not configured, show the example binding from the report and say where the file goes. Tell the user to keep credentials in the environment and name them under envFrom rather than writing them into the file.
If an extension is reported as unavailable or failed, relay the reason exactly as given — a command that is not there, a server that did not answer — and do not guess at a fix beyond what the report says.
Say plainly that the context still works: its profile and knowledge folder are served whether or not any extension is configured.
To record that this context expects something new:
node "<plugin-root>/src/codex/neatcontext-cli.mjs" extensions add <id> --capability "<what it lets this context do>"
Add --tools a,b to narrow it to specific tools, and --important when the context leans on it. That records what the context wants; it connects nothing on its own. extensions remove <id> drops the declaration and leaves any local binding alone, and extensions test <id> starts one on purpose and names the tools it really offers.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 32 lines · 45 tokens per session scan A e310056e31dd
extensions is a skill published in the GitHub repository XTSoftwareLabs/neatcontext-plugins (13 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 423 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
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.
pipeline-auto
Use when the user wants a substantial feature taken from idea through implementation in one run with as little interruption as possible ("just build it", "don't keep asking me"), or when controlling such a run and a worker question, quorum responses, the drift budget, a human decision, a review class or a completeness…
turbo-pipeline
Use when the user wants a feature built end to end after answering one round of questions and then being left alone — "turbo", "ask me once, then just build it", "I'll answer up front, don't come back to me", "decide the rest yourself". Not for a run that wants a spec approval and no tests (superb:fast-pipeline), one…
bug-fix
Use when a bug, regression, or unexpected behaviour is reported and the user wants it fixed end to end — "why is X broken", "this stopped working after Y", "fix this crash". Also use when a symptom is known but its cause is not. Not for building new behaviour, and not for a change whose cause is already proven.
fast-pipeline
Use when the user wants a feature built quickly with low token cost and few interruptions, approves a spec once, and says no automated tests should be written because they will test it manually — "fast pipeline", "go fast, no tests, I'll test it myself", "don't keep asking me". Not for a run that should write or keep…