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/Typiqally/lintropyWrote 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/typiqally/lintropy/claude-code)<a href="https://agentmods.dev/plugins/typiqally/lintropy/claude-code"><img src="https://agentmods.dev/badge/plugins/typiqally/lintropy/claude-code/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/typiqally/lintropy/claude-code"><img src="https://agentmods.dev/badge/plugins/typiqally/lintropy/claude-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lintropy-lsp 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
{
"description": "Registers `lintropy lsp` as a Language Server so Claude Code sees lintropy diagnostics live while editing.",
"homepage": "https://github.com/Typiqally/lintropy",
"license": "MIT",
"lspServers": {
"lintropy": {
"args": [
"lsp"
],
"command": "lintropy",
"extensionToLanguage": {
".cts": "typescript",
".go": "go",
".mts": "typescript",
".py": "python",
".pyi": "python",
".rs": "rust",
".ts": "typescript",
".tsx": "typescriptreact",
".yaml": "yaml",
".yml": "yaml"
}
}
},
"name": "lintropy-lsp",
"repository": "https://github.com/Typiqally/lintropy",
"version": "0.1.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 — 0 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 · 29 lines scan A fa72bb47eb96
lintropy-lsp is a plugin published in the GitHub repository Typiqally/lintropy (5 stars, last pushed 4mo 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-31.
Other plugins, from other repositories
docvet-lsp
Real-time docstring quality diagnostics for Python files.
brooks-lint
AI code reviews grounded in twelve classic engineering books — decay risk diagnostics with book citations, severity labels, and six analysis modes (PR review, architecture audit, tech debt, test quality, health dashboard, full-sweep auto-fix).
codeeraser
CodeEraser passive guard + erase skill: a winnowing clone index behind a per-project daemon intercepts T1/T2 duplicate writes at PreToolUse (with the tombstone and flow legs judged in the core), records at PostToolUse whether an asked write ran (settle), audits net LOC + touched duplicates at Stop, and reports health…
antidote
Stop AI agents from patching symptoms. Forces structural root-cause fixes over symptom patching in any language or stack.
lumen
Precise local semantic code search via MCP. Indexes your codebase with Go AST parsing, embeds with Ollama or LM Studio, and exposes vector search to Claude through an MCP server — no cloud, no npm.
cpp-lsp
Claude Code plugin for C/C++ development with clangd LSP integration, 14 automated hooks for compilation, linting (clang-tidy), formatting (clang-format), and memory analysis (valgrind).