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/alejandrosaenz117/bonfires-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/alejandrosaenz117/bonfires-marketplace/osv-scanner)<a href="https://agentmods.dev/plugins/alejandrosaenz117/bonfires-marketplace/osv-scanner"><img src="https://agentmods.dev/badge/plugins/alejandrosaenz117/bonfires-marketplace/osv-scanner/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/alejandrosaenz117/bonfires-marketplace/osv-scanner"><img src="https://agentmods.dev/badge/plugins/alejandrosaenz117/bonfires-marketplace/osv-scanner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
osv-scanner 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 21d 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": "osv-scanner",
"version": "0.1.1",
"description": "Scans project dependencies for known vulnerabilities using OSV Scanner and the OSV database.",
"author": {
"name": "Alejandro Saenz",
"url": "https://github.com/alejandrosaenz117"
},
"license": "MIT",
"privacyPolicyUrl": "https://github.com/alejandrosaenz117/bonfires-marketplace/blob/main/plugins/osv-scanner/PRIVACY.md",
"supportUrl": "https://github.com/alejandrosaenz117/bonfires-marketplace/issues",
"homepage": "https://github.com/alejandrosaenz117/bonfires-marketplace",
"repository": "https://github.com/alejandrosaenz117/bonfires-marketplace",
"keywords": [
"security",
"vulnerabilities",
"dependencies",
"osv",
"scanning",
"SCA",
"software composition analysis"
],
"mcpServers": {
"osv-scanner": {
"command": "osv-scanner",
"args": ["experimental-mcp"]
}
}
}
What it installs
The manifest is a name and a version. 1 skill, 2 commands travel with it, and installing the plugin installs all of them — 142 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.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.
- 21d ago Changed · +2 lines d78a0502e65e
- 1mo ago First seen · 28 lines scan A 951ea2e838bf
osv-scanner is a plugin published in the GitHub repository alejandrosaenz117/bonfires-marketplace (4 stars, last pushed 22d 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
gh-review-loop
Clears AI reviewer feedback on your PR: reads real review-thread state, sweeps the sibling instances the reviewer missed, gates every push on your repo's own tests, then requests re-review — hard-capped at 3 re-review requests. Claude Code, Codex, Gemini and Copilot built in; any reviewer bot can be configured.
pharaoh
Codebase knowledge graph with focused development workflow skills. Query architecture, dependencies, blast radius, and more instead of reading files one at a time.
code-review
Iterative code review toolkit. Bundles two skills: code-review (diff-based PR review or holistic codebase audit with gap detection and tracked fix loop) and address-pr-review (validate GitHub PR comments, fix, reply, and resolve threads).
punchcard
Architecture-level code review from a fifty-year veteran: design, boundaries, data and error paths — never naming or formatting. One verdict, every finding that earns its place, every claim demonstrated in code. Reviews a diff in the conversation or posts one review into a GitHub PR / GitLab MR. Briefs a change before.
dev-loop
Three commands for the daily loop in Claude Code: fix a bug or apply a review report, commit with pre-flight checks, or run review, fix and commit as one flow, pausing after the review for your go-ahead.
dev-workflow-forge
Generate a code review skill and coding rules fitted to your own repository, then improve them from what your reviews keep finding. You start each generator yourself, and the learning loop asks before it applies any change.