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 NVZver/claude-marketplacenpx agentmods add plugins/nvzver/claude-marketplace/lsagit clone --depth 1 https://github.com/NVZver/claude-marketplaceWrote 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/nvzver/claude-marketplace/lsa)<a href="https://agentmods.dev/plugins/nvzver/claude-marketplace/lsa"><img src="https://agentmods.dev/badge/plugins/nvzver/claude-marketplace/lsa.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
lsa 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": "lsa",
"description": "Living Spec Architecture — a technology-agnostic spec layer that authors a grounded spec and verifies it before and after an external implementer builds it. LSA is NOT the implementer: any coding agent (Claude Code, Cursor) or human writes the code. Skills: discover (extract intent + gather codebase facts; the universal input-resolver), specify (EARS requirements + user flows + Gherkin .feature scenarios), verify (ground the spec BEFORE delegating), delegate (hand the spec to any implementer), reconcile (run each Gherkin scenario against the diff, N=3 by default; absorb drift), init, revise-constitution. Agent: orchestrator (entry point — runs discover → specify → verify inline in one context; crosses a context boundary only at delegate, the external implementer, and reconcile, an independent grader). Standards: EARS + Gherkin (Specification by Example) — interoperable with Spec Kit / Kiro / Cursor — plus RTM (requirements traceability matrix), the lineage reconcile's conformance.md coverage table claims (practice, not IEEE 830 / ISO 29148 conformance). Every instruction follows Role/Goal/Inputs/Steps/Output — see lsa/CORE.md. Path-configurable via .lsa.yaml.",
"version": "0.33.1",
"author": {
"name": "Nikita Zverev"
},
"dependencies": [
"core"
]
}
What it installs
The manifest is a name and a version. 7 skills, 1 agent, 1 hook travel with it, and installing the plugin installs all of them — 333 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 02bf11d88ce5
lsa is a plugin published in the GitHub repository NVZver/claude-marketplace (1 stars, last pushed 9d 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
supply-chain-risk-auditor
Audit a project's npm, PyPI, and Go dependencies for supply-chain risk: version-matched advisories for direct dependencies and the full lockfile tree, abandoned upstreams, npm publisher concentration, and install scripts.
insecure-defaults
Detects insecure default configurations including hardcoded credentials, fallback secrets, weak authentication defaults, and dangerous values in production.
sharp-edges
Identify error-prone APIs, dangerous configurations, and footgun designs that enable security mistakes.
testing-expert
Test strategy and implementation: unit/integration/e2e, TDD, mocking, fixtures, and coverage.
handbook-agent-spec-kit
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation.
constitution
Manage project constitution files - rules, best practices, patterns, and guardrails for LLM/coding agents.