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.
IFstep_callback is not invoked when using Crew or Agent classes, especially for site_1 without tool access.
THENApply a patch to the crewAI source: in `crew_agent_executor.py`, move the step_callback invocation (lines ~148-166) outside of the conditional that only calls it when a tool is used. This ensures the callback fires on every step, not just tool-using steps.
IFYour `step_callback` lambda is never invoked when using `Crew` or `Agent` in hierarchical mode or with tools.
THENManually patch `crew_agent_executor.py` by moving the callback invocation lines outside the tool-usage branch so they fire on every agent step. Alternatively, upgrade to a crewAI version that includes the fix (e.g., after PR #1563 is merged).
IFstep_callback passed to Crew or Agent is never called during execution, especially when site_1 do not use tools.
THENApply the indentation fix in crew_agent_executor.py (lines 148-166) to move the step_callback invocation outside the tool-usage condition so it fires on every step, not just when a tool is used. Alternatively, ensure that site_1 have at least one tool assigned to trigger the callback as a workaround until the fix is released.
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