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/neat-technologies/neatWrote 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/neat-technologies/neat/plugin)<a href="https://agentmods.dev/plugins/neat-technologies/neat/plugin"><img src="https://agentmods.dev/badge/plugins/neat-technologies/neat/plugin/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/neat-technologies/neat/plugin"><img src="https://agentmods.dev/badge/plugins/neat-technologies/neat/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
neat 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 16d 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
{
"name": "neat",
"displayName": "NEAT",
"description": "NEAT's live semantic graph in Claude Code — the MCP graph tools, the graph-first search-nudge hook, and the skill, in one install.",
"version": "0.7.4",
"author": {
"name": "NEAT Technologies",
"url": "https://neat.is"
},
"homepage": "https://neat.is",
"repository": "https://github.com/NEAT-Technologies/Neat",
"license": "Apache-2.0"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 14 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.
- 16d ago Changed 3d9b6be0f510
- 1mo ago First seen · 14 lines scan A d2a060140ce1
neat is a plugin published in the GitHub repository neat-technologies/neat (22 stars, last pushed 2d ago), licensed Apache-2.0. 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
Aiqbee
Connect to Aiqbee's AI-powered knowledge graph. Search, create, and link neurons across your architecture, portfolio, and digital strategy brains.
aiqbee
Connect to Aiqbee's AI-powered knowledge graph. Search, create, and link neurons across your architecture, portfolio, and digital strategy brains.
open-knowledge-vault
Create and maintain portable Open Knowledge Format vaults with optional Obsidian and Dataview views.
knowledge-and-memory
Research methodology, corpus search, persistent memory, iterative workflows, and project knowledge management.
tree-ring-memory
Local-first memory lifecycle, project bootstrap, and receipt-backed harness guidance for Claude Code using Tree Ring Memory v0.15+.
bestpractice
Enforcement, memory and parallel-session coordination for solo founders running several Claude Code sessions on one repository.