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/wellwelwel/laguneWrote 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/wellwelwel/lagune/gemini)<a href="https://agentmods.dev/plugins/wellwelwel/lagune/gemini"><img src="https://agentmods.dev/badge/plugins/wellwelwel/lagune/gemini/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/wellwelwel/lagune/gemini"><img src="https://agentmods.dev/badge/plugins/wellwelwel/lagune/gemini.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lagune 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 yesterday.
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": "lagune",
"description": "๐ชผ Your security copilot as you build, your Blue Team when you audit, whether you're a developer or not.",
"version": "0.18.0",
"contextFileName": [],
"mcpServers": {
"lagune": {
"command": "node",
"args": [
"lib/bin/index.js",
"mcp",
"${workspacePath}"
],
"cwd": "${extensionPath}"
}
}
}
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.
- yesterday Changed d652c6efab41
- 2d ago Changed 97f6bfa117bf
- 3d ago Changed ยท +4 lines c396b24087a9
- 5d ago First seen ยท 14 lines scan A 9a2d579401fb
lagune is a plugin published in the GitHub repository wellwelwel/lagune (173 stars, last pushed yesterday), 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-11-02.
lagune compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| lagunewellwelwel/lagune | Plugin | 173 | yesterday | Apache-2.0 | A | โ | Gemini CLI |
| identity-securityzero-lab-ai/skills | Plugin | 168 | 22d ago | Apache-2.0 | A | โ | Claude Code |
| recon-operationszero-lab-ai/skills | Plugin | 168 | 22d ago | Apache-2.0 | A | โ | Claude Code |
| plugin-templatezero-lab-ai/skills | Plugin | 168 | 22d ago | Apache-2.0 | A | โ | Claude Code |
| taskmastereyaltoledano/claude-task-master | Plugin | 28k | 6mo ago | none | A | โ | Claude Code |
| humanizerblader/humanizer | Plugin | 65k | 9d ago | MIT | A | โ | Claude Code |
| claude-plugins-official marketplaceanthropics/claude-plugins-official | Plugin | 46k | yesterday | Apache-2.0 | A | โ | Claude Code |