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
3
Categories
2258
Tier-1 (public)
4,089
Tier-2 (your patterns)
private to your site
bedrock_guardrails
security-bedrock-guardrails-when-using-bedrock-guardrails-with-the-post-call-h-137080f5
IFWhen using Bedrock Guardrails with the post_call hook only, guardrails are not applied to input content, leaving prompt injection or harmful inputs unchecked.
THENConfigure both pre_call and post_call modes in the LiteLLM proxy to ensure guardrails run on both input and output. For example, in the proxy config, set 'guardrails: ["pre_call", "post_call"]' for the Bedrock guardrail definition.
Tier 170%
bedrock_guardrails
security-bedrock-guardrails-when-using-bedrock-guardrails-with-disable-excepti-43706a6b
IFWhen using Bedrock guardrails with `disable_exception_on_block: true`, a blocked prompt's guardrail response is sent to the model instead of being returned directly to the user, causing unnecessary token usage.
THENUpgrade LiteLLM to the version containing the fix (commit referenced in the issue) so that pre-call guardrail blocks return the guardrail response directly without invoking the model. Alternatively, set `disable_exception_on_block: false` and handle the HTTP 400 exception in your client by catching it and displaying the guardrail's modified output to the user.
Tier 170%
bedrock_guardrails
security-bedrock-guardrails-when-disable-exception-on-block-is-set-to-true-in--2ee478b8
IFWhen disable_exception_on_block is set to true in LiteLLM, pre-call Bedrock Guardrails that block content forward the guardrail response to the model instead of returning it to the user.
THENSet disable_exception_on_block to false (default) to raise an HTTP 400 exception on block, and update client applications (e.g., Open WebUI, Claude Code) to handle that exception gracefully. Alternatively, wait for the fix in LiteLLM v1.74.7+ that returns the guardrail response directly without invoking the model.
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