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.
IFUser implements a Claude API call without specifying model version, thinking, or streaming.
THENDefault to `claude-opus-4-7` as model string. Use adaptive thinking (`thinking: {type: "adaptive"}`) for complex tasks. Enable streaming for long I/O to avoid timeouts; use `.get_final_message()` to collect full response.
IFLiteLLM proxy sets max_tokens to 4096 for Claude 3.5/3.7 when not specified, but the correct default is 8192.
THENUpdate the default max_tokens for Anthropic Claude 3.5 and 3.7 models to 8192, or configure the model provider in litellm by setting the max_tokens field to 8192 in the proxy configuration. This ensures the proxy uses the full output capacity of these models. Alternatively, warn users to explicitly set max_tokens to avoid artificial output limitations.
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