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 init-repogit 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/init-repo)<a href="https://agentmods.dev/skills/filip-podstavec/claude-leverage/init-repo"><img src="https://agentmods.dev/badge/skills/filip-podstavec/claude-leverage/init-repo/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/init-repo"><img src="https://agentmods.dev/badge/skills/filip-podstavec/claude-leverage/init-repo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
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 →
- high YARA Match · line 3 YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
- high Prompt Injection · line 93 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 113 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00079 | $0.01987 |
| Opus 5 | $0.00039 | $0.00993 |
| Sonnet 5 | $0.00016 | $0.00397 |
| Haiku 4.5 | $0.00008 | $0.00199 |
Grade A, and why
init-repo 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 11d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/init-repo
What it does
Sets up a fresh (or existing) repository to use the claude-leverage stack's conventions:
- AGENTS.md — drops a customized copy of
templates/AGENTS.md.example, with placeholders filled in from the detected project name, stack, and conventions. - CLAUDE.md — creates a one-line
@AGENTS.mdimport file so Claude Code sees the canonical guidance. - .gitignore — appends a block (between markers) ignoring the
stack's local state dirs (
.last-stack-check, session-nudge files) and per-language artifacts that would otherwise show up in/repo-mapnoise. - Logging template (optional, per detected language) — drops the
matching
templates/logging/<lang>.mdbody into a sensible path in the project (e.g.,src/<pkg>/logging_setup.py). - AIDEV-NOTE convention reminder — a single line at the top of the new AGENTS.md pointing at the spec.
Each step is confirmed before write. Re-running detects already- installed sections via marker comments and offers update-in-place.
Workflow
-
Resolve target dir. Default cwd. If
$ARGUMENTShas a path, use that. Verify it's a git repo (git rev-parse --show-toplevelfrom the target). If not, ask the user: "this isn't a git repo —git initfirst, or proceed anyway?" -
Detect language from file presence. Check in order:
package.json→ TypeScript / Node.jspyproject.toml/setup.py/requirements.txt→ Pythongo.mod→ GoCargo.toml→ Rust- Mixed / none → ask the user, default
none. - Override with
--langflag.
-
Read project name from manifest (
package.json#name,pyproject.toml [project] name,go.modfirst line,Cargo.toml [package] name). Fall back to directory name. -
Plan the changes as a numbered list. Show the user:
I'll add the following to <target-dir>: 1. AGENTS.md — customized for <lang>, project name <name> 2. CLAUDE.md — single @AGENTS.md import line 3. .gitignore — append claude-leverage state patterns (~5 lines) 4. <pkg>/logging_setup.<ext> — structured-logging starter Proceed? (y / n / select-subset)Unless
--noninteractive, wait for confirmation. With--noninteractive, write all 4.
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.
- 11d ago First seen · 186 lines · 79 tokens per session scan A 049bd13e0fdb
init-repo is a skill published in the GitHub repository Filip-Podstavec/claude-leverage (68 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 1,987 once invoked, about $0.0004 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.