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 agentmods add skills/sjarmak/agent-workflows/convergenpx skills add sjarmak/agent-workflows --skill convergegit clone --depth 1 https://github.com/sjarmak/agent-workflowsWrote 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/sjarmak/agent-workflows/converge)<a href="https://agentmods.dev/skills/sjarmak/agent-workflows/converge"><img src="https://agentmods.dev/badge/skills/sjarmak/agent-workflows/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 | $0.00000 | $0.01386 |
| Opus 5 | $0.00000 | $0.00693 |
| Sonnet 5 | $0.00000 | $0.00277 |
| Haiku 4.5 | $0.00000 | $0.00139 |
Grade A, and why
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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- converge — 86% identical, 29 lines differ
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Structured debate and refinement using Agent Teams. Takes divergent findings (from /diverge or any independent research) and spawns a team where teammates advocate for different positions, debate trade-offs, and converge on a refined synthesis.
Arguments
$ARGUMENTS — format: [N] [path/to/diverge_output.md or inline topic] where N is optional number of debaters (default: 3, min 2, max 5)
Prerequisites
- Agent Teams must be enabled (
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1) - Input should be divergent findings — either a file path to prior /diverge output, a PRD with open tensions, or a description of competing approaches
Parse Arguments
Extract:
- team_size: optional leading integer (default 3, min 2, max 5)
- input: path to a file with divergent findings, or inline description of the debate topic
Phase 0: Validate Teams Availability
Check that Agent Teams is enabled. If not, inform the user:
Agent Teams is required for /converge. Enable it by adding to your Claude Code settings:
"env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" }
Or use /diverge for independent exploration without debate.
Phase 1: Frame the Debate
If a file path is provided: read the file and extract the key tensions, divergence points, and competing recommendations.
If inline input: parse the competing positions from the description.
If neither is clear: ask the user what positions or findings should be debated.
Prepare a debate brief that includes:
- The core question or decision to be made
- 2-5 distinct positions to be advocated (one per teammate)
- Shared context and constraints all positions must respect
- Evaluation criteria: what makes one approach better than another?
Present the debate brief and position assignments to the user for confirmation.
Phase 2: Spawn the Team
Create an agent team with the following structure:
Team Lead (you): Moderator and synthesizer. You frame rounds, call for responses, and produce the final synthesis.
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.
- 5d ago First seen · 147 lines · 0 tokens per session scan A e5cc0d2e5c89
converge is a skill published in the GitHub repository sjarmak/agent-workflows (9 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,386 tokens. 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-31.
Other skills, from other repositories
speckit.specify
Skill "speckit.specify" from caipe-io/ai-platform-engineering, covering user input, outline, quick guidelines, section requirements and for ai generation.
speckit.clarify
Skill "speckit.clarify" from caipe-io/ai-platform-engineering, covering user input and outline.
local-integration-testing
Run end-to-end integration tests with all 15 agents and supervisor in local Docker Compose dev environment. Validates agent discovery, multi-agent routing, checkpoint persistence, and cross-agent follow-up conversations.
release-docs
Generate a combined release blog post for ai-platform-engineering. Produces a single docs/releases/YYYY-MM-DD-release-X-Y-Z.md file containing release notes and the upgrade guide (migration guide) inline. Use when cutting a release, when a user asks "what changed in 0.4.x", or when upgrading their values.yaml to a new…
update-docs
Audit and update all documentation moving parts for ai-platform-engineering. Checks release blog posts, features page, agent docs, homepage version strings, Docusaurus version config, and sidebar completeness. Fixes what is stale and reports what needs manual attention. Use after cutting a release, adding a new agent…
docker-compose-first-install
Validate and repair the OSS first-install Docker Compose path. Use when editing docker-compose.yaml, docker-compose.dev.yaml, .env.example, release image tags, Compose profiles, Keycloak/OpenFGA/RAG defaults, or first-launch UI behavior for local all-in-one installs.