/Lagune

Instead of running a generic checklist, what if security existed before, during, and after development?

claude plugin install lagune --marketplace wellwelwel/lagune

Builds what your prompt asks for, with security guarding the work as it happens, not later.

/lagune
Example

Lagune is your security copilot as you build, your Blue Team when you audit.

Whether you're a developer or not.

00:0000:00

Harden as you build

One command, /lagune, brings security while the code is written, not after.

Mark it on any prompt and the agent builds what you asked for as always, now with security knowledge on-demand.

Inspired by Spec-Driven

A five-phase, Blue Team-based flow, ready to run.

It detects what your system actually does, maps the matching attack vectors, then applies the security work that fits.

Knowledge on demand

Focused security modules load only for what your project is.

It pulls in the module that fits the context it finds, drawing from a catalog that keeps adapting as new risks emerge.

Progress in your browser

A local, private dashboard follows your findings, fixes, and proofs live.

Live view of your project's security, as the agent works. It runs on your machine and nothing leaves it.

/lagune-charter
Add this to your agent's instructions file, such as AGENTS.md or CLAUDE.md, as one of its first instructions:
## Security
- Whenever you build or change code, use the `/lagune` skill (named `/lagune:lagune` when installed as a plugin), to improve safety by default.

Then, use the /lagune skill on any prompt, at any time, to build more securely.