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 sjarmak/coding-agent-workflows --skill divergegit clone --depth 1 https://github.com/sjarmak/coding-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/coding-agent-workflows/diverge)<a href="https://agentmods.dev/skills/sjarmak/coding-agent-workflows/diverge"><img src="https://agentmods.dev/badge/skills/sjarmak/coding-agent-workflows/diverge/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/sjarmak/coding-agent-workflows/diverge"><img src="https://agentmods.dev/badge/skills/sjarmak/coding-agent-workflows/diverge.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.00034 | $0.01307 |
| Opus 5.5 | $0.00014 | $0.00523 |
| Sonnet 5.5 | $0.00007 | $0.00261 |
| Haiku 4.5 | $0.00003 | $0.00131 |
Grade A, and why
diverge 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 1mo 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diverge: Multi-Perspective Divergent Research
Spawn N independent agents with uncorrelated context windows to explore a question from different angles, then auto-synthesize their findings into a unified analysis and PRD.
Arguments
[N] "research question or topic"
- N is the number of agents (default 3, min 2, max 7).
- The question is the research topic. Missing or unclear: ask the user to clarify before starting.
Phase 1: Frame the Research
Before spawning agents, frame the research space. Write a short research brief (3-5 bullet points) that:
- States the core question
- Lists known constraints or context from the conversation
- Identifies 2-3 dimensions of exploration (e.g., technical feasibility, workflow design, prior art)
Present this to the user and confirm before proceeding. Adjust if the user gives feedback.
Phase 2: Spawn Independent Agents
Launch all N agents in parallel using the Agent tool. Each agent MUST:
-
Have a unique research lens: assign each a distinct angle, perspective, or methodology. Examples:
- "Prior art and industry patterns" (what exists, what others do)
- "First-principles technical design" (bottom-up from constraints)
- "User experience and workflow" (developer ergonomics, day-in-the-life)
- "Failure modes and risks" (what can go wrong, edge cases)
- "Scale and evolution" (how this grows, maintenance burden)
- "Contrarian/devil's advocate" (challenge assumptions, explore alternatives)
-
Receive the same research brief but with their unique lens clearly stated
-
Be instructed to:
- Research independently (web search, codebase exploration, reasoning)
- Produce a structured output with: Key Findings (3-5), Concrete Recommendations (2-3), Open Questions, and a Confidence Assessment
- NOT be told what other agents are exploring
- Think creatively within their lens, surprising or non-obvious insights are more valuable than safe ones
-
Use
subagent_type: "general-purpose"(they need web search, file access, etc.)
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.
- 1mo ago First seen · 191 lines · 34 tokens per session scan A 116b85aad1b0
diverge is a skill published in the GitHub repository sjarmak/coding-agent-workflows (6 stars, last pushed 17d ago), licensed MIT. It adds 34 tokens to every session and 1,307 once invoked, about $0.0001 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-31.
Other skills, from other repositories
browser-trace
Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page…
planning-with-files
Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…
ai-elements
Build AI chat interfaces using ai-elements components — conversations, messages, tool displays, prompt inputs, and more. Use when the user wants to build a chatbot, AI assistant UI, or any AI-powered chat interface.
exa-search
Use Exa MCP for current web, code/docs, company, people, and page-fetch research. Prefer current hosted tool schemas and note deprecated tools.
ontoly-software-graph
Use Ontoly's deterministic Software Graph and MCP capabilities for repository architecture, request tracing, dependency analysis, configuration lookup, and impact analysis before falling back to source search.
kimi-webbridge
A way for an AI agent to control the user's real web browser, including pages where the user is already signed in. It can navigate, click, type, read page content, and take screenshots.