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/Alberto-Codes/docvetWrote 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/alberto-codes/docvet/marketplace)<a href="https://agentmods.dev/plugins/alberto-codes/docvet/marketplace"><img src="https://agentmods.dev/badge/plugins/alberto-codes/docvet/marketplace/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/alberto-codes/docvet/marketplace"><img src="https://agentmods.dev/badge/plugins/alberto-codes/docvet/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade 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 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.
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"
}
]
}
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
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.
- 1mo 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 today), 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
Set up, run and fix MegaLinter on any repository: 100+ linters for 69+ languages, 23+ formats and 21+ tooling formats, from CI or locally.
oat-publish-python
Python release management: cleanup, version bump, uv build, GitHub release, publish monitoring.
oat-cleanup
Code quality pipeline: ruff linting/formatting, mypy type checking, pytest.
python-lsp
Claude Code plugin for Python development with Pyright LSP integration, 15 automated hooks for type checking, linting (ruff), formatting (black), testing (pytest), and security scanning.
kernel-sdks
TypeScript and Python SDK skills for building browser automation with Kernel's Typescript and Python SDKs.