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 Filip-Podstavec/claude-leveragenpx agentmods add plugins/filip-podstavec/claude-leverage/marketplacegit clone --depth 1 https://github.com/Filip-Podstavec/claude-leverageWrote 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/filip-podstavec/claude-leverage/marketplace)<a href="https://agentmods.dev/plugins/filip-podstavec/claude-leverage/marketplace"><img src="https://agentmods.dev/badge/plugins/filip-podstavec/claude-leverage/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
filip-podstavec 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 6d 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": "filip-podstavec",
"owner": {
"name": "Filip Podstavec",
"url": "https://github.com/Filip-Podstavec"
},
"plugins": [
{
"name": "claude-leverage",
"source": {
"source": "url",
"url": "https://github.com/Filip-Podstavec/claude-leverage.git"
},
"description": "Personal Claude Code + Codex dev stack: security hooks, AI-first code conventions, 16 on-demand skills (incl. /repo-doctor — AI-readiness audit with code↔docs drift detection — and /refresh-context-map for the v1.8.0 smart-context-surfacing hook), ADR + session-log conventions, portable statusline. Complements other skills-based plugins, not a replacement.",
"version": "1.16.0",
"category": "workflow",
"keywords": [
"ai-first",
"security-review",
"codex",
"claude-code",
"agents-md",
"repo-map",
"statusline",
"stack-freshness"
]
}
]
}
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
1 file 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.
- 6d ago First seen · 30 lines scan A e23c578aad9b
filip-podstavec marketplace is a plugin published in the GitHub repository Filip-Podstavec/claude-leverage (68 stars, last pushed 1mo 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
ask-llm
AI-to-AI collaboration — review code and debate plans across Codex, Grok, Antigravity, Ollama, and Gemini.
skill-bus
The skill for connecting skills. Connect context, conditions, and other skills to any skill — no modification required.
canvas-design
Create beautiful visual art in PNG and PDF documents using design philosophy. Use for posters, art pieces, designs, or other static visual works with museum-quality craftsmanship.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
security-guidance
Security reminder hook that warns about potential security issues when editing files, including command injection, XSS, and unsafe code patterns.
repo-doctor
Diagnostic skills for GitHub repos. Currently ships readme-doctor — a structured review of a repo's README against best-practice patterns (hero presence, install-to-first-success length, audience match, drift signals), output as a prioritized punch list.