Borrowing it
Nothing to install: this file belongs to moberghr/mtk-agent-toolkit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/moberghr/mtk-agent-toolkit/main/.claude/skills/setup-converge/SKILL.mdgit clone --depth 1 https://github.com/moberghr/mtk-agent-toolkitWrote 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/moberghr/mtk-agent-toolkit/setup-converge)<a href="https://agentmods.dev/skills/moberghr/mtk-agent-toolkit/setup-converge"><img src="https://agentmods.dev/badge/skills/moberghr/mtk-agent-toolkit/setup-converge.svg" alt="Measured on agentmods" 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.00037 | $0.02588 |
| Opus 5 | $0.00018 | $0.01294 |
| Sonnet 5 | $0.00007 | $0.00518 |
| Haiku 4.5 | $0.00004 | $0.00259 |
Grade B, and why
setup-converge scanned grade B with 1 finding 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 7d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
4. Otherwise, fall back to `find ~/.claude/plugins -maxdepth 8 -name "SKILL.md" -path "*/mtk/*/context-engineering/*" -type f 2>/dev/null | sort -V | tail -1 | sed 's|/.claude/skills/context-engineering/SKILL.md||'`. If How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MTK Setup Converge — Code Judged Against Agreed Principles
MTK File Resolution
MTK skills and shared references live either in the project (local install) or the plugin cache (marketplace install). Resolve once:
- If
$MTK_HELPER_ROOTis set, prefix.claude/skills/and.claude/references/reads with it — a pinned checkout wins over every other source. - Otherwise, if
$CLAUDE_PLUGIN_ROOTis set, prefix them with that. - Otherwise, if
.claude/skills/context-engineering/SKILL.mdexists locally → project-relative paths work as-is. - Otherwise, fall back to
find ~/.claude/plugins -maxdepth 8 -name "SKILL.md" -path "*/mtk/*/context-engineering/*" -type f 2>/dev/null | sort -V | tail -1 | sed 's|/.claude/skills/context-engineering/SKILL.md||'. If empty, MTK skills are unavailable — warn the engineer and proceed withCLAUDE.mdonly.
Always project-relative (never prefixed): CLAUDE.md, .claude/tech-stack, .claude/rules/, tasks/, docs/, .claude/references/architecture-principles.md, .claude/references/pre-commit-review-list.md, .mtk/ (workflow state). Resolve skills and scripts from the same root: a split (skills from a local dev checkout, scripts from the plugin cache) risks version drift — anchor both the same way.
This skill is the inverse of setup-refresh: refresh keeps the docs honest about the code; converge keeps the code honest about the docs. It treats architecture-principles.md (and conventions.md, where stamped) as normative and reports where the codebase has drifted from what the team already agreed to — as reviewable, graded work items, never as an in-place fix. Converge is read-only outside .claude/.mtk-cache/; it never edits the audited docs, never edits source, and never appends to tasks/todo.md without an explicit interactive approval (STEP 5).
STEP 0: Preconditions
Require both a prior bootstrap AND at least one stamped doc to judge code against:
test -f .claude/tech-stack || MISSING_TECH_STACK=1
test -f .claude/mtk-version.json || MISSING_VERSION=1
STAMPED_DOCS=()
for doc in .claude/references/architecture-principles.md .claude/references/conventions.md; do
[ -f "$doc" ] && grep -q '<!-- mtk-stamp' "$doc" && STAMPED_DOCS+=("$doc")
done
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.
- 7d ago First seen · 154 lines · 37 tokens per session scan B 49d9885c249f
setup-converge is a skill published in the GitHub repository moberghr/mtk-agent-toolkit (7 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 2,588 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…