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.
git 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/observer)<a href="https://agentmods.dev/plugins/nvzver/claude-marketplace/observer"><img src="https://agentmods.dev/badge/plugins/nvzver/claude-marketplace/observer/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/plugins/nvzver/claude-marketplace/observer"><img src="https://agentmods.dev/badge/plugins/nvzver/claude-marketplace/observer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade 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 1mo 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 it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 288 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.
- 1mo ago First seen · 12 lines scan A 2053041c25dc
observer is a plugin published in the GitHub repository NVZver/claude-marketplace (1 stars, last pushed 1mo 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
code-craftsmanship
Code quality and software design skills including Clean Code (Robert C. Martin), Refactoring patterns (Martin Fowler), A Philosophy of Software Design (John Ousterhout), The Pragmatic Programmer (Hunt & Thomas), Domain-Driven Design (Eric Evans), Working Effectively with Legacy Code (Michael Feathers), and Google's…
systems-architecture
Systems architecture and distributed systems skills including Designing Data-Intensive Applications (Martin Kleppmann), System Design Interview (Alex Xu), Clean Architecture (Robert C. Martin), Release It! (Michael Nygard), High Performance Browser Networking (Ilya Grigorik), and Team Topologies (Skelton & Pais).
product-strategy
Product strategy and innovation frameworks including Jobs to Be Done (Clayton Christensen) for customer discovery and product design, tactical negotiation skills (Chris Voss), willingness-to-pay pricing (Monetizing Innovation), and startup metrics (Lean Analytics).
handbook-dotnet
.NET development skills: running single C# files, testing, coverage, API inspection, analyzers and Roslyn queries.
handbook-discover
Discover and audit all plugins in a Claude Code marketplace with installation status, versions, and component breakdown.
handbook-team-stack
Interactive skill that analyzes a task, proposes an agent team composition, and creates the team after user confirmation.