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.
npx skills add Filip-Podstavec/claude-leverage --skill adr-newgit 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/skills/filip-podstavec/claude-leverage/adr-new)<a href="https://agentmods.dev/skills/filip-podstavec/claude-leverage/adr-new"><img src="https://agentmods.dev/badge/skills/filip-podstavec/claude-leverage/adr-new/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/skills/filip-podstavec/claude-leverage/adr-new"><img src="https://agentmods.dev/badge/skills/filip-podstavec/claude-leverage/adr-new.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 105 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00106 | $0.01411 |
| Opus 5 | $0.00053 | $0.00705 |
| Sonnet 5 | $0.00021 | $0.00282 |
| Haiku 4.5 | $0.00011 | $0.00141 |
Grade A, and why
adr-new 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/adr-new
What it does
Creates a new numbered ADR file in docs/adr/ and adds an entry to the
index. ADRs are the lightweight memory of why the architecture looks
the way it does — without them, six months from now nobody (human or
agent) remembers why we chose A instead of B.
The convention is documented in
docs/adr/README.md: MADR-flavored,
numbered, immutable status (proposed → accepted → deprecated /
superseded).
Workflow
-
Find target dir. Default
docs/adr/from the current repo root (viagit rev-parse --show-toplevel). If nodocs/adr/exists, ask the user: "create it now?". If yes, also copytemplates/adr-template.mdif shipped (the plugin ships its own template underdocs/adr/template.md— useful as a reference even when the target repo doesn't have one yet). -
Pick next number. List existing
docs/adr/NNNN-*.mdfiles, parse the leading number, take the max + 1. Pad to 4 digits. -
Get the title.
- If
$ARGUMENTShas a positional, use it as the title. - If
--noninteractive, fail if no title was given (we won't hallucinate one). - Otherwise, prompt the user.
- Convert to kebab-case for the filename:
0042-replace-polling-with-webhooks.md.
- If
-
Ask for context (skip in
--noninteractive):- One-line summary of the problem.
- The chosen option (one sentence, stated as fact in present tense).
- 1–3 alternatives considered (one line each).
- Whether to mark
status: proposed(default) oraccepted(if the team already decided in conversation and just needs the record).
-
Generate the file at
docs/adr/<NNNN>-<kebab-title>.mdusing the MADR template (the plugin shipsdocs/adr/template.mdfor reference). Substitute:NNNN→ resolved numberTitle→ user-provided titleYYYY-MM-DD→ today (date +%Y-%m-%d)Status→ resolved value- Context / Decision / Alternatives → user input or
<TODO: fill in>placeholders if user skipped them
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.
- 10d ago First seen · 137 lines · 106 tokens per session scan A bc02682da03d
adr-new is a skill published in the GitHub repository Filip-Podstavec/claude-leverage (68 stars, last pushed 1mo ago), licensed MIT. It adds 106 tokens to every session and 1,411 once invoked, about $0.0005 per session on Opus 5. 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 skills, from other repositories
OCR Review-to-Approval Loop
Drive a PR to an approved code review by looping OCR's multi-agent review and address steps. Runs /ocr:review then /ocr:address repeatedly until the review verdict is APPROVE, then one final /ocr:address for leftover suggestions, posting every review and every address round to the GitHub PR as comments. Use when the…
repo-visuals
Create hero visuals — animated GIF, static PNG, or animated SVG — for GitHub repositories. Runs a structured discovery conversation (scan repo → recommend format → propose creative scenarios → agree on a brief), then designs bespoke HTML/SVG, previews it in the browser, and exports. Use when the user asks for a README…
opik
This skill should be used when the user needs to add Opik tracing or integrations to their code, instrument an LLM application, or needs reference for Opik SDK usage (Python, TypeScript, REST API). Use for tasks like "add tracing", "instrument my code", "use trackopenai", "add OpikTracer", "what span types are…
hyper-plan
Use when about to start a non-trivial implementation that needs decomposition before coding. Also when the user invokes /hyperclaude:hyper-plan. Produces an ordered, bite-sized plan in .hyperclaude/plans/ — the input for /hyperclaude:hyper-plan-review and /hyperclaude:hyper-implement.
swarm
Run a multi-agent audit of a codebase by spawning specialized parallel subagents (security, performance, tests, architecture, dead-code), then synthesize their findings into a single prioritized action plan. Use this whenever the user runs /swarm, asks to "audit the repo," "review this codebase," "find issues across…
tools-unity-behavior-designer
Behavior Designer patterns for AI behavior trees including task creation, shared variables, conditionals, and debugging.