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 litellm with langfuse_otel callback, LLM calls inside a decorated function are not nested under the parent span, appearing as separate traces.
THENManually pass the parent's OTEL span to the completion call via metadata key "litellm_parent_otel_span". Create a child span from the parent's OTEL span (e.g., using langfuse_client.start_span) and set the metadata to include that span. This ensures the LLM invocation is traced as a child of the parent span.
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