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.
npx skills add wellwelwel/lagune --skill engineeringgit 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/skills/wellwelwel/lagune/engineering)<a href="https://agentmods.dev/skills/wellwelwel/lagune/engineering"><img src="https://agentmods.dev/badge/skills/wellwelwel/lagune/engineering/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/skills/wellwelwel/lagune/engineering"><img src="https://agentmods.dev/badge/skills/wellwelwel/lagune/engineering.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 51 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00039 | $0.01232 |
| Opus 5.5 | $0.00016 | $0.00493 |
| Sonnet 5.5 | $0.00008 | $0.00246 |
| Haiku 4.5 | $0.00004 | $0.00123 |
Grade A, and why
engineering 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 17d 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering
This skill is the specialized, authoritative description of how code is written: the code conventions, the comment discipline, the type rules, testing, and commit messages. Consult it before writing or changing source, and whenever you apply the code conventions.
Where the project already has an established convention that contradicts one below, follow the project. These rules decide whatever the project leaves open.
Code conventions
Security
- Use the
/laguneskill (lagune.ai), whenever you build or change code, so it improves safety by default. If it is not available, runnpx -y lagune@latest pullto install it from its manifest.- When there is no manifest, suggest to the user how to initialize Lagune.
General
- Arrow functions over
function. Declare withconst. Use afunctiononly when thethiscontext strictly requires it. - Named exports only. Never use
default export. - Practice early return. Handle edge cases up front and exit, rather than nesting the main logic.
- No abbreviations. Names are clear and explicit (for example
left/right, nota/b, andindex, noti). - Avoid nested
if-else-else-if. Favor clean, well-decoupled approaches when branching grows. - No duplicated logic or types. Reuse existing logic and types whenever it is viable.
- No side effects inside loops or iterations. Keep iteration pure.
- Prefer native capabilities over external dependencies whenever possible.
- On Node.js, always prefix native imports with
node:(for examplenode:path,node:fs). - Prefer the async native APIs when viable (for example
node:fs/promises).
Layout
- Shared declarations live at the top of the file or scope. Anything used by more than one block is declared before the first block that uses it, never between blocks. Order them by kind: types first, then values and fixtures, then functions.
- Group statements by kind, and separate the groups with one blank line. Consecutive declarations stay together, consecutive calls stay together, and the switch from one kind to the other gets a blank line, even when a group holds a single statement. The same rule applies inside callbacks and between top-level declarations.
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.
- 17d ago Changed · +7 lines · -12 tokens per session db32f60a99c3
- 1mo ago First seen · 61 lines · 51 tokens per session scan A 8b2fc7ff8bf8
engineering is a skill published in the GitHub repository wellwelwel/lagune (173 stars, last pushed 5d ago), licensed MIT. It adds 39 tokens to every session and 1,232 once invoked, about $0.0002 per session on Opus 5.5. 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 skills, from other repositories
octocode-benchmark
Use when planning, running, grading, or reporting the by-hand Octocode research benchmark — pairwise matchups (Octocode anchor vs one baseline: gh+RTK, gh+Headroom, or plain gh) over markdown questions, with a fresh isolated runner agent per (question, arm, pass), one blind judge per question grading two answers X/Y…
112-java-maven-plugins
Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) …
patrol-e2e-testing
Use when writing E2E/integration tests, testing native interactions like permissions or system dialogs, capturing UI regressions, or validating cross-platform behavior (Patrol 4.x).
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
mockito
Use when generating mocks, stubbing methods, verifying interactions, capturing arguments, or choosing between mocks, fakes, and real objects (Mockito).
mocktail
Use when creating mocks, stubbing methods, verifying interactions, registering fallback values, or choosing between mocks, fakes, and real objects (Mocktail).