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.
git 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/plugins/xtsoftwarelabs/neatcontext-plugins/neatcontext)<a href="https://agentmods.dev/plugins/xtsoftwarelabs/neatcontext-plugins/neatcontext"><img src="https://agentmods.dev/badge/plugins/xtsoftwarelabs/neatcontext-plugins/neatcontext/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/plugins/xtsoftwarelabs/neatcontext-plugins/neatcontext"><img src="https://agentmods.dev/badge/plugins/xtsoftwarelabs/neatcontext-plugins/neatcontext.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
neatcontext 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "neatcontext",
"displayName": "NeatContext",
"version": "0.3.5",
"description": "Save Claude Code work as reusable, domain-aware context",
"author": {
"name": "XTSoftwareLabs",
"url": "https://github.com/XTSoftwareLabs"
},
"homepage": "https://github.com/XTSoftwareLabs/neatcontext-plugins",
"repository": "https://github.com/XTSoftwareLabs/neatcontext-plugins",
"license": "MIT",
"keywords": ["neatcontext", "context", "knowledge-management", "grounding", "mcp"],
"mcpServers": {
"neatcontext": {
"command": "node",
"args": ["${CLAUDE_PLUGIN_ROOT}/src/claude/mcp-bridge.mjs"]
}
}
}
What it installs
The manifest is a name and a version. 11 commands travel with it, and installing the plugin installs all of them — 119 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 22 lines scan A aa796dc6d5da
neatcontext is a plugin published in the GitHub repository XTSoftwareLabs/neatcontext-plugins (13 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
superb
Personal skill collection for Claude Code and Codex, invoked as superb: . setup installs what the others need; craft turns a vague product idea into a decision-rich brief; pipeline v2 drives a settled idea through approved file-backed plans and durable execution state to a finished branch; pipeline-auto does the.
continuity
Intentional session continuity for Claude Code: /wrap writes a retro, a tooling-journal entry and a NEXTSESSION.md handoff; /next reads the handoff and past retros; a SessionStart hook says when a handoff exists.
programme
Carry a multi-session programme across session boundaries: a durable ledger, an interviewed handoff, and a guard that fires when a session changes code without moving the record.
repo-indexer
Indexes and documents codebases for persistent Claude context with minimal token overhead. Creates tiered memory (native memory + CLAUDE.md + on-demand files + conversation history) so Claude remembers your projects across sessions.
security
Threat modeling, security architecture review, incident response, vulnerability management, and access and identity. Reviewer-class: blocking findings are not overrulable by the department under review.
data-analytics
Data governance, warehouse and semantic modeling, business intelligence, and AI/ML governance.