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 liuyanghejerry/Clausura --skill code-review-with-lspgit clone --depth 1 https://github.com/liuyanghejerry/ClausuraWrote 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/liuyanghejerry/clausura/code-review-with-lsp)<a href="https://agentmods.dev/skills/liuyanghejerry/clausura/code-review-with-lsp"><img src="https://agentmods.dev/badge/skills/liuyanghejerry/clausura/code-review-with-lsp/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/liuyanghejerry/clausura/code-review-with-lsp"><img src="https://agentmods.dev/badge/skills/liuyanghejerry/clausura/code-review-with-lsp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00040 | $0.00546 |
| Opus 5 | $0.00020 | $0.00273 |
| Sonnet 5 | $0.00008 | $0.00109 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
code-review-with-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 11d 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
Code Review with LSP
This skill works with
mcp_servers+preflightin.clausura.yaml. Preflight diagnostics are collected automatically; this skill guides the agent to use LSP tools for deeper semantic analysis.
Review Workflow
For each file or diff hunk under review:
Step 1. Check diagnostics
Call mcp__<server>__get_diagnostics (or equivalent) for the file.
Preflight results are already in context — but if diagnostics were not
automatically collected, run them now.
Record every diagnostic as a finding:
rule_id:lsp-<diagnostic-type>(e.g.lsp-type-mismatch)severity: map 1:1 from diagnostic severitymessage: keep the original diagnostic message verbatim
Step 2. Understand unfamiliar symbols
When you encounter a symbol, function, or type you need to understand:
- hover — get type signature and docs:
mcp__<server>__hover - definition — jump to the definition:
mcp__<server>__goto_definition - references — check all callers:
mcp__<server>__find_references
Step 3. Check for cascading impact
If a change affects a public API or core type:
- Use
mcp__<server>__find_referencesto find all callers - Check if those callers handle the new signature correctly
Finding Severity Mapping
| LSP Severity | Finding Severity | When |
|---|---|---|
| Error | error |
Compile error, type mismatch, undefined reference |
| Warning | warning |
Deprecation, unused variable, non-fatal lints |
| Information | info |
Style hints, auto-fix suggestions |
| Hint | hint |
Minor suggestions, organizational hints |
Example Rule IDs for Gating
gating:
# LSP diagnostics (rule_id_prefix: "lsp-")
- rule: lsp-type-mismatch
min_severity: error
max_findings: 0
action: fail
- rule: lsp-compile-error
min_severity: error
max_findings: 0
action: fail
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.
- 11d ago First seen · 67 lines · 40 tokens per session scan A cd29d212d2f3
code-review-with-lsp is a skill published in the GitHub repository liuyanghejerry/Clausura (203 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 546 once invoked, about $0.0002 per session on Opus 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
setup-pre-commit
Use when bootstrapping or extending the pre-commit hook chain (Husky + lint-staged + Prettier + typecheck + integration tests) for an EVOKORE-style TypeScript repo, including detecting an existing setup, surfacing the diff, and never silently overwriting a configured chain.
quality-gate
Use when you need to check if current work meets quality thresholds before proceeding to the next phase or merging.
pull-request-feedback-loop
Handles PR review feedback by fetching comments, grouping issues, fixing one group at a time, and verifying before replies.
claude-c-suite-cto
Use for architecture, tech debt, refactoring, dependency, scaling, migration, and codebase health reviews.
claude-c-suite-dx-lead
Use for developer experience, API ergonomics, SDK usability, docs quality, onboarding, and error-message reviews.
claude-c-suite-audit
Use when auditing or release-checking the Claude C-Suite plugin's own command conformance.