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/observergit clone --depth 1 https://github.com/NVZver/claude-marketplaceGrade A, and why
observer 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 2d 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": "observer",
"description": "Live observe-and-coach discipline for the NVZver marketplace. Rides Claude Code's self-paced /loop through two Actors. observer:observe reacts to your file changes through a chosen role (rubber-duck, pair-programmer, interviewer, custom), read as data from one Knowledge file (roles.md). observer:verify-checkpoint gates an implementer's increment: on a checkpoint signal it grades that one F-requirement does·only (not the whole-plan all check — that stays with lsa:reconcile) and emits CLEAR (auto-clears) or BLOCK (surfaced to the human), read-only to the graded artifacts. Depends on core (ground-rules, output).",
"version": "0.3.3",
"author": {
"name": "Nikita Zverev"
},
"dependencies": [
"core"
]
}
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.
- 2d ago First seen · 12 lines scan A 2053041c25dc
observer is a plugin published in the GitHub repository NVZver/claude-marketplace (1 stars, last pushed 8d 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.
ck
Cavekit — compressed spec-driven dev. Full loop (grill → spec → research → review → build) over one SPEC.md file: three core commands + four reach-for. Caveman encoding. Bug-to-spec backprop.
handbook-agent-spec-kit
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation.
handbook-qa
Browser automation and QA testing tools with Playwright MCP integration.