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.
IFWhen using Ollama or Bedrock with Llama3 models, the stop token `<|eot_id|>` is not included by default, causing the model to generate endlessly.
THENExplicitly pass the stop token `stop=["<|eot_id|>"]` when initializing ChatOllama or ChatBedrock. Also ensure `langchain-community` is updated to at least version 0.0.33 to include the latest fixes.
IFLlama 3 via LangChain LlamaCpp produces nonsensical output when context length exceeds approximately 4k tokens.
THENSet the `rope_freq_base` parameter to 500000 (or recalculate for extended context) and ensure `rope_freq_scale` is not overridden by LangChain's hardcoded defaults. Pass these as `model_kwargs` to `LlamaCpp` or set them directly in the constructor if supported. Verify the model metadata shows the correct value.
IFYou want to add observability to existing LLM frameworks with minimal code changes.
THENUse Langfuse's drop-in replacements or callback handlers for OpenAI, LangChain, LlamaIndex, Haystack, etc.
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