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 Alberto-Codes/docvetnpx agentmods add plugins/alberto-codes/docvet/marketplacegit clone --depth 1 https://github.com/Alberto-Codes/docvetGrade A, and why
docvet 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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- docvet-lsp — 88% identical, 41 lines differ
What it actually says
{
"name": "docvet",
"owner": {
"name": "Alberto-Codes"
},
"metadata": {
"description": "Docvet Python docstring quality tools for Claude Code"
},
"plugins": [
{
"name": "docvet-lsp",
"source": {
"source": "github",
"repo": "Alberto-Codes/docvet"
},
"description": "Real-time docstring quality diagnostics for Python files",
"homepage": "https://alberto-codes.github.io/docvet/",
"repository": "https://github.com/Alberto-Codes/docvet",
"license": "MIT",
"keywords": ["python", "docstrings", "linting", "code-quality", "lsp"],
"category": "code-intelligence"
}
]
}
What ships with it
2 files 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 · 25 lines scan A bd71147d5e4e
docvet marketplace is a plugin published in the GitHub repository Alberto-Codes/docvet (9 stars, last pushed 18d 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
megalinter
Set up, run and fix MegaLinter on any repository: 100+ linters for 69+ languages, 23+ formats and 21+ tooling formats, from CI or locally.
megalinter marketplace
MegaLinter agent plugin: set up, run and fix MegaLinter from your coding agent.
blockwatch
Keep co-dependent code, docs, and config in sync with BlockWatch annotations: drift detection (affects), sorted/unique lists, regex/line-count/AI/Lua validation. Includes a skill that teaches agents when and how to add and maintain blocks.
hi-vibe
Vibe-coding seatbelt for Claude Code — doc automation (CLAUDE.md/MODULE.md/handover/CHANGELOG) + AI discipline (root-cause first, no unfounded claims) + machine enforcement (ruff/eslint/import cycles).
purist
A single skill that hardens the style checkers and static analyzers already wired into a project: discovers every configuration in place, raises each tool to its strictest practical setting, and adds a list of custom rules on top — it cranks what is configured rather than introducing a new toolchain.
claudeconf
Research-driven, technology-agnostic harness generator for Claude Code: pinned, standard-tool quality + security pipelines (git hooks, CI, e2e, gates, supply-chain admission, agent-hardening) plus a read-only harness-doctor agent.