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 ooloth/dotfiles --skill review-convergegit clone --depth 1 https://github.com/ooloth/dotfilesWrote 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/ooloth/dotfiles/review-converge)<a href="https://agentmods.dev/skills/ooloth/dotfiles/review-converge"><img src="https://agentmods.dev/badge/skills/ooloth/dotfiles/review-converge/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/ooloth/dotfiles/review-converge"><img src="https://agentmods.dev/badge/skills/ooloth/dotfiles/review-converge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00057 | $0.04814 |
| Opus 5.5 | $0.00023 | $0.01926 |
| Sonnet 5.5 | $0.00011 | $0.00963 |
| Haiku 4.5 | $0.00006 | $0.00481 |
Grade A, and why
review-converge 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 Changed · +2 lines b559d9ea8373
- 1mo ago Changed · +53 lines 9d51dab64343
- 1mo ago Changed · -5 tokens per session 0fa72f6b5fd4
- 1mo ago Changed · +127 lines 47270ad0851a
- 1mo ago First seen · 296 lines · 62 tokens per session scan A 517b5e2a52f0
review-converge is a skill published in the GitHub repository ooloth/dotfiles (24 stars, last pushed today), with no licence file. It adds 57 tokens to every session and 4,814 once invoked, about $0.0002 per session on Opus 5.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
pr-review
Intelligent PR code review with dynamic agent allocation based on change types. Analyzes PR changes and generates targeted review tasks.
analyze-pr
Analyze a GitHub/GitLab Pull Request by fetching its diff, reading its web description, and generating a comprehensive document. Use when the user provides a PR link and wants to understand what changes the PR introduces, or asks to review/analyze/summarize a pull request.
merge-ready
Drive an existing pull request to a mergeable state: get CI green, resolve merge conflicts with the base branch, address and resolve review comments, trigger required bot reviews/approvals (e.g. commenting '@claude review'), link associated issues, and clean up the PR title and description. Ends with a readiness…
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
source-drafting
Use when drafting documents, reports, posts, presentations, or review comments from source materials, or conducting research across provided documents. Enforces read-first drafting, a source map for every claim, agent verification, and separation of verified from unverified claims.
smart-commit
Analyze staged changes and split them into multiple logical commits following Conventional Commits.