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 oliver-kriska/claude-elixir-phoenixnpx agentmods add plugins/oliver-kriska/claude-elixir-phoenix/lvgit clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenixWrote 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/oliver-kriska/claude-elixir-phoenix/lv)<a href="https://agentmods.dev/plugins/oliver-kriska/claude-elixir-phoenix/lv"><img src="https://agentmods.dev/badge/plugins/oliver-kriska/claude-elixir-phoenix/lv.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
lv 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 today.
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": "lv",
"version": "3.1.0",
"description": "Compatibility namespace for the Elixir/Phoenix plugin's /lv:* commands",
"author": {
"name": "Oliver Kriska"
},
"homepage": "https://github.com/oliver-kriska/claude-elixir-phoenix",
"repository": "https://github.com/oliver-kriska/claude-elixir-phoenix"
}
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.
- today First seen · 11 lines scan A cf278f3ca310
lv is a plugin published in the GitHub repository oliver-kriska/claude-elixir-phoenix (537 stars, last pushed 3d 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-09-03.
Other plugins, from other repositories
procoder
A harness that gives AI coders the tools and skills to work like a senior developer. All nine domains shipped: security, best practices, maintainability, performance, documentation, clean code, CI/CD, DevOps, GitOps — plus the code index. Hooks hand the agent results; the agent stays in control.
the-bulwark
Full-lifecycle SDLC guardrailing framework for Claude Code — from product ideation and planning through implementation, code review, and test validation. Enterprise-grade skills and agents for AI-human peer collaboration.
x-dev-pipeline
Structured dev workflow with spec, requirements, execution, verify, qa-gate, fix loops, and audits.
high-quality-projects-skill
Production-oriented project discovery and code standards for any coding agent. projectsetup runs a multi-round Grill Me interview, inventories branding and existing project material, confirms product and delivery decisions, then reuses or extends canonical work before scaffolding strict quality gates. qualityretrofit.
fable-discipline
Fable's engineering discipline for any Claude session, with one habit enforced by a hook. Two layers: running the task (stage, verify each stage with a failable check, written done-criteria) and writing the code (recon before edit, verify against a copy with a negative self-test, single-writer chokepoints…
git-workflow
5 git workflow skills: create worktrees/branches (from the current position or a named base branch), open PRs with an AI-drafted title/body, and clean up branches/worktrees after merge.