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 voxpelli/vp-claudenpx agentmods add plugins/voxpelli/vp-claude/marketplacegit clone --depth 1 https://github.com/voxpelli/vp-claudeWrote 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/voxpelli/vp-claude/marketplace)<a href="https://agentmods.dev/plugins/voxpelli/vp-claude/marketplace"><img src="https://agentmods.dev/badge/plugins/voxpelli/vp-claude/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
vp-plugins marketplace 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 5d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "vp-plugins",
"description": "Knowledge graph management and sprint workflow automation for Claude Code",
"owner": {
"name": "Pelle Wessman"
},
"plugins": [
{
"name": "vp-knowledge",
"source": "./",
"description": "Multi-ecosystem package research (npm, Rust, Go, PHP, Python, Ruby) with Socket supply-chain scoring, developer tool research (Homebrew with MCP analytics, GitHub Actions, Docker, VSCode, gh CLI extensions, Claude Code plugins, skills.sh bundles), multi-ecosystem version-drift detection (brew, npm, cask, crate, vscode, plugin), person research, knowledge gap analysis (incl. host-installed plugin/skill coverage), scope-partitioned graph audit/fix skills, project context priming, Readwise integration, session bookmarking, tag vocabulary sync, a Claude Code feature-adoption learning-nudge system, graph maintenance agents, and quality hooks for Basic Memory",
"version": "0.34.2"
},
{
"name": "vp-beads",
"source": {
"source": "github",
"repo": "voxpelli/claude-beads"
},
"description": "Sprint workflow automation: backlog grooming, retrospectives, upstream vendor tracking, cross-project synergy tracking, swarm wave orchestration, vendor sync, and bilateral sibling reconciliation for projects using beads and Basic Memory",
"version": "0.18.0"
},
{
"name": "vp-git",
"source": {
"source": "github",
"repo": "voxpelli/claude-git"
},
"description": "Git workflow safety skills for stacked-PR chains: rebase-validate (five-layer pipeline \u2014 range-diff, sem, weave, jscpd, tests), stack-cascade (safety-tagged rebase --update-refs with atomic force-with-lease push), and tag-audit (SHA-grouped triage of accumulated safety tags with KEEP/DROP confirmation gate). Installable as a Claude Code plugin or via the cross-agent Agent Skills standard (skills.sh)",
"version": "0.8.0"
},
{
"name": "vp-astgrep",The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 43 lines scan A 4a3041b95347
vp-plugins marketplace is a plugin published in the GitHub repository voxpelli/vp-claude (3 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
vp-beads
Sprint workflow automation: backlog grooming, retrospectives, upstream vendor tracking, cross-project synergy tracking, swarm wave orchestration, vendor sync, and bilateral sibling reconciliation for projects using beads and Basic Memory.
claude-wiki-pages
A Claude Code plugin for Obsidian — Karpathy's LLM Wiki shipped as a four-layer, hook-enforced agent stack with multi-agent orchestration.
membrain
Graph-based agent memory — search, trace, and manage what your agent knows.
capture
Capture session information into a staging file for later reflection and knowledge graph processing.
neatcontext marketplace
Save Claude Code work as reusable, domain-aware context.
neatcontext
Save Claude Code work as reusable, domain-aware context.