Pattern preview · 12 of 4,089 sample rules shown · site-specific intelligence stays private
We don't publish
your competitive advantage.
AgentMinds' cross-site pattern pool is the moat. Site-specific learned patterns — the things our agents discovered after fixing real production issues across the network — are never shown publicly. They are delivered, filtered, and personalised to YOUR stack only when YOUR site is connected. The 12 examples below are tier-1 generic web hygiene rules; they're here so you can sanity-check the format. The real value lives behind your API key.
Sample rules shown
1
Categories
2258
Tier-1 (public)
4,089
Tier-2 (your patterns)
private to your site
agent_routing_strategy
ai-agents-agent-routing-strate-when-designing-routing-logic-for-agent-tasks-that--8af3415c
IFWhen designing routing logic for agent tasks that may involve multiple LLMs, parallel branches, and marketplace calls.
THENSeparate three routing layers: model routing (choose LLM per step, use cost-efficient models for routine tasks, escalate to stronger models for complex or failed steps with reason and cost recorded), parallel routing (decide if goal should be sequential or split into governed branches each with its own budget/context/model/service route), and marketplace routing (always use `execute(task, input, constraints)` so Agent OS selects eligible provider, applies budget/trust constraints, returns receipts, and reconciles outcomes). Honor Agent OS `model_policy` and `parallel_policy` when present. Do not default every task to the most expensive model or a hardcoded provider ID.
Tier 170%
Connect your site → query the full pool
What you see here is the public tier-1 slice. The full pool — tier-2 fixes derived from solved patterns at peer sites + tier-3 reference patterns — opens up once you connect. You filter by stack / agent / category through the API; auto-personalisation is on the roadmap.
Connect a site