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 conventions-initgit 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/conventions-init)<a href="https://agentmods.dev/skills/filip-podstavec/claude-leverage/conventions-init"><img src="https://agentmods.dev/badge/skills/filip-podstavec/claude-leverage/conventions-init/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/conventions-init"><img src="https://agentmods.dev/badge/skills/filip-podstavec/claude-leverage/conventions-init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00124 | $0.01090 |
| Opus 5 | $0.00062 | $0.00545 |
| Sonnet 5 | $0.00025 | $0.00218 |
| Haiku 4.5 | $0.00012 | $0.00109 |
Grade A, and why
conventions-init 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 9d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/conventions-init
What it does
Bootstraps conventions.yml at the repo root — the profile the context-surface
hook surfaces to an agent before it edits a source file (casing rules, a
vague-name denylist, directory roles, and divergent house rules the model cannot
infer). Block-style YAML only, so the stdlib fallback parser stays reliable.
It infers the mechanical parts (casing, structure) and asks the user for the house rules — it never invents a convention the repo does not actually hold.
When to invoke
- Setting up an AI-first repo, after
/init-repo. - When you want the plugin to start steering on this repo (no
conventions.ymlyet means the whole steering loop is a no-op).
Do NOT invoke for: per-function docs (those are docstrings), or to auto-write house rules the team has not agreed on.
Workflow
- Resolve repo root (
git rev-parse --show-toplevel); if not a repo, STOP and suggestgit init//init-repo. - Detect mode. If
conventions.ymlis absent, bootstrap. If it exists, do NOT rewrite it (stdlib YAML loses the human-writtenconsistencycomments); instead print the suggested draft below and tell the user to merge by hand. - Infer casing. Run
python scripts/score_adherence.py --repo .if the plugin's scorer is available, and readmetrics.casing_consistency.by_kind[*] .dominantforfunctions/types/constants. Python-first: if there are no.pyfiles (or the scorer is absent), leavecasingvalues blank with a comment for the user — never guess from an unsupported language. - Seed structure roots. List top-level + recognized source dirs (
src/,lib/,app/,scripts/,tests/, …) that exist; write each as a root key with a blank role string for the user to fill. - Seed the denylist from the documented defaults (
data,result,tmp,handle,process); the user can extend. - Leave
consistencyas a commented template — house rules are the user's to write (same "never invent" rule asglossary-init). - Write
conventions.yml(bootstrap mode) with theschema_version"1.x" comment, block-style. In existing-file mode, print the draft instead. - Remind the user to run
/refresh-context-mapso the manifest (and thus the hook) picks up the new conventions, and offer a one-lineAGENTS.mdpointer. - Report the path and which fields were inferred vs left for the user.
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.
- 9d ago First seen · 97 lines · 124 tokens per session scan A de6ff0bb4176
conventions-init is a skill published in the GitHub repository Filip-Podstavec/claude-leverage (68 stars, last pushed 1mo ago), licensed MIT. It adds 124 tokens to every session and 1,090 once invoked, about $0.0006 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…
mcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).