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/divergenpx skills add sjarmak/agent-workflows --skill divergegit 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/diverge)<a href="https://agentmods.dev/skills/sjarmak/agent-workflows/diverge"><img src="https://agentmods.dev/badge/skills/sjarmak/agent-workflows/diverge.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.00000 | $0.01282 |
| Opus 5 | $0.00000 | $0.00641 |
| Sonnet 5 | $0.00000 | $0.00256 |
| Haiku 4.5 | $0.00000 | $0.00128 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-perspective divergent research. Spawns N independent agents with uncorrelated context windows to explore a question from different angles, then auto-synthesizes findings into a unified analysis and PRD.
Arguments
$ARGUMENTS — format: [N] "research question or topic" where N is optional (default: 3)
Parse Arguments
Extract:
- agent_count: the optional leading integer (default 3, min 2, max 7)
- research_prompt: the quoted or unquoted research question/topic
If the research prompt is missing or unclear, ask the user to clarify before proceeding.
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
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 · 185 lines · 0 tokens per session scan A 39eb5a34123a
diverge 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,282 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.