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.
/plugin marketplace add 4rgon4ut/cc-zig-lspnpx agentmods add plugins/4rgon4ut/cc-zig-lsp/cc-zig-lspgit clone --depth 1 https://github.com/4rgon4ut/cc-zig-lspWrote 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/4rgon4ut/cc-zig-lsp/cc-zig-lsp)<a href="https://agentmods.dev/plugins/4rgon4ut/cc-zig-lsp/cc-zig-lsp"><img src="https://agentmods.dev/badge/plugins/4rgon4ut/cc-zig-lsp/cc-zig-lsp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
zig-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 3d 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": "zig-lsp",
"description": "Zig language support via ZLS (auto-installs)",
"version": "0.1.1",
"author": {
"name": "4rgon4ut"
},
"repository": "https://github.com/4rgon4ut/cc-zig-lsp",
"keywords": ["zig", "lsp", "zls", "language-server"],
"lspServers": "./.lsp.json"
}
What it installs
The manifest is a name and a version. 1 hook travel with it, and installing the plugin installs all of them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json 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.
- 3d ago First seen · 12 lines scan A e8267d180a00
zig-lsp is a plugin published in the GitHub repository 4rgon4ut/cc-zig-lsp (4 stars, last pushed 2mo 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
xcode-build-skills
A multi-skill plugin for benchmarking and optimizing Xcode builds, compile hotspots, project settings, and Swift Package Manager dependency overhead.
go-ultimate
Opinionated Go development skill — architecture, conventions, production readiness, repo/CI hygiene, review, and MCP/agent patterns.
kernel-sdks
TypeScript and Python SDK skills for building browser automation with Kernel's Typescript and Python SDKs.
swift-performance-pro
Performance: Instruments, SwiftUI render cost, memory and retain cycles, launch time, lists.
hyperstack
Disciplined MCP server + skill system. 12 plugins and 80 tools covering designer (6 personalities, 13 page templates, 9 presets), shadcn/ui, design tokens, ui/ux, React Flow v12, Motion v12, Lenis, React 19, Echo, Go, and Rust. 22 skills with adversarial enforcement: Iron Laws, 1% Rule, rationalization tables, and…
mcp-apps-builder
Build, modify, debug, migrate, review, or verify TypeScript MCP servers and MCP Apps with mcp-use.