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 process-diagramgit 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/process-diagram)<a href="https://agentmods.dev/skills/filip-podstavec/claude-leverage/process-diagram"><img src="https://agentmods.dev/badge/skills/filip-podstavec/claude-leverage/process-diagram/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/process-diagram"><img src="https://agentmods.dev/badge/skills/filip-podstavec/claude-leverage/process-diagram.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Prompt Injection · line 29 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.00065 | $0.01276 |
| Opus 5 | $0.00032 | $0.00638 |
| Sonnet 5 | $0.00013 | $0.00255 |
| Haiku 4.5 | $0.00006 | $0.00128 |
Grade A, and why
process-diagram 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/process-diagram
What it does
Produces a Mermaid diagram for a named workflow (the flow of
/security-review, how a hook intercepts a Bash call, how the
SessionStart bare-repo-nudge decision tree resolves, etc.) and
optionally inserts it into a target markdown file between idempotent
markers:
<!-- process-diagram:<name>:start -->
```mermaid
sequenceDiagram
...
## Workflow
1. **Parse arguments.**
- First positional arg: the workflow name (snake_case). Becomes the
diagram's identifier in the markers.
- `--into <path>`: target markdown file to insert into. If omitted,
just print the diagram to the user.
- `--type sequence|flowchart`: override the auto-pick. Default rule:
sequence diagrams for inter-component flows (actors talking to each
other), flowcharts for decision logic / state transitions.
2. **Resolve the workflow.** Three sources, in order:
- If a SKILL.md or command file with the workflow's name exists in
`skills/` or `commands/`, Read it for the participants and steps.
- If the user describes the workflow in conversation, use that.
- Otherwise, ask the user for participants and the 3–10 steps. Do not
hallucinate a flow.
3. **Generate the mermaid.**
- For `sequenceDiagram`: list participants first (`participant U as User`,
`participant M as Main session`, …), then the message arrows. Use
`->>` for sync, `-->>` for response, `Note over` for annotations.
- For `flowchart`: use `flowchart LR` (or `TB` if the user prefers).
Wrap labels containing special characters (parens, colons, slashes)
in double quotes — Mermaid's parser bails on bare ones (per the
known issue documented in `docs/specs/research/research_visualization.md`).
- Avoid Mermaid reserved IDs: `end`, `class`, `subgraph`. Pick
descriptive IDs (`User`, `MainSession`, `SecurityReviewer`).
4. **Validate with mmdc if available.**
- Write the mermaid to a temp file (`mktemp`).
- Run `mmdc -i <tmp.mmd> -o <tmp.svg> 2>&1`.
- If non-zero: read the error message, fix the specific issue, retry.
Cap at 3 retries — if still failing, surface the mermaid + error to
the user and let them decide.
- If `mmdc` is not on PATH: skip validation with a one-line warning.
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 · 122 lines · 65 tokens per session scan A dc0b4425e570
process-diagram is a skill published in the GitHub repository Filip-Podstavec/claude-leverage (68 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 1,276 once invoked, about $0.0003 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.