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/bencium/bencium-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/bencium/bencium-marketplace/vanity-engineering-review)<a href="https://agentmods.dev/plugins/bencium/bencium-marketplace/vanity-engineering-review"><img src="https://agentmods.dev/badge/plugins/bencium/bencium-marketplace/vanity-engineering-review.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
vanity-engineering-review 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 8d 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": "vanity-engineering-review",
"version": "1.0.0",
"description": "Reviews codebases, architectures, PRs, and technical plans for vanity engineering — code built for the developer's ego rather than delivering user or business value.",
"author": { "name": "bencium.io", "url": "https://bencium.io" },
"keywords": ["code-review", "architecture", "over-engineering", "complexity", "simplification"]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 181 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 8d ago First seen · 8 lines scan A a6487ac51e78
vanity-engineering-review is a plugin published in the GitHub repository bencium/bencium-marketplace (419 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-30.
Other plugins, from other repositories
code-guardian
Automated code review, security scanning, and quality enforcement.
code-review-assistant
Automated code review with severity levels and actionable feedback.
complexity-reducer
Reduce cyclomatic complexity and simplify functions.
double-check
Verify code correctness with systematic second-pass analysis.
fix-pr
Fix PR review comments automatically with context-aware patches.
a11y-audit
Full accessibility audit with WCAG compliance checking.