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 MustaphaSteph/vorec-pluginsnpx agentmods add plugins/mustaphasteph/vorec-plugins/marketplacegit clone --depth 1 https://github.com/MustaphaSteph/vorec-pluginsGrade A, and why
vorec-plugins 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": "vorec-plugins",
"description": "Official Vorec plugins for Claude Code",
"owner": {
"name": "Vorec",
"email": "[email protected]"
},
"plugins": [
{
"name": "record-tutorial",
"description": "Record screen and generate narrated tutorial videos with AI voice-over.",
"version": "14.44.0",
"source": "./",
"author": {
"name": "Vorec",
"email": "[email protected]"
}
}
]
}
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.
- 2d ago First seen · 21 lines scan A 5a2b5a43eaf2
vorec-plugins is a plugin published in the GitHub repository MustaphaSteph/vorec-plugins (7 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
playwright-bot-bypass
Stealth browser automation — bypass bot detection with rebrowser-playwright / undetected-chromedriver.
docpull
Pull public web sources into Claude Code. Indexes static and server-rendered sites as local Markdown with conditional-GET caching, then exposes them as MCP tools. Local, browser-free, no API keys.
verefi-marketplace
Verefi plugins for human-reviewed Playwright test automation.
repo-agent-harness
Lay the foundation that makes a repository teach coding agents how to work in it: delivery moments wired to hooks, a layered docs truth source, CI gates plus tool-call guards, a rebuildable repo graph, and a consolidation pass. Bootstraps once, then the repo stands on its own.
living-manual
Plugin marketplace listing 1 plugin: living-manual.
skill-engine
Teach Claude your codebase, then keep it taught. On opt-in, clones registered git sources to a local cache (/.cache/skill-engine/) and installs per-skill context files under your project's .claude/skills/. Reads only paths you register.