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
tool_input_validation
ai-agents-tool-input-validatio-nl2sqltool-fails-with-pydantic-validation-error-sq-f0771e15
IFNL2SQLTool fails with pydantic validation error: 'sql_query' field missing, because the tool receives a dictionary keyed as 'query' instead of 'sql_query'.
THENEnsure the tool invocation passes the correct parameter name 'sql_query'. If the agent or task automatically maps input keys differently, either rename the input in the tool schema or modify the task definition to output the key 'sql_query'. Alternatively, create a wrapper tool that renames 'query' to 'sql_query'.
Tier 170%
tool_input_validation
ai-agents-tool-input-validatio-nl2sql-tool-fails-with-validation-error-sql-query--0924c0ab
IFNL2SQL tool fails with validation error 'sql_query' field required but input contains 'query'
THENThe NL2SQL tool's input schema expects 'sql_query', but the agent passes a dictionary with key 'query'. To fix, either modify the tool's Pydantic model to accept an alias for 'query' or ensure the agent's task inputs use the correct key 'sql_query'. As a workaround, manually map 'query' to 'sql_query' before passing to the tool.
Tier 170%
tool_input_validation
ai-agents-tool-input-validatio-sporadic-400-error-from-bedrock-tools-3-custom-inp-74ed72a1
IFSporadic 400 error from Bedrock: 'tools.3.custom.input_examples: Extra inputs are not permitted' when using Claude Code with LiteLLM.
THENEnsure tool definitions do not include the 'input_examples' field. Either downgrade Claude Code to v2.0.36 (which does not send this field) or implement a custom LiteLLM middleware to strip unsupported nested fields from tool definitions before sending to Bedrock. The 'drop_params: true' setting only handles top-level parameters, not nested tool properties.
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