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
2
Categories
2258
Tier-1 (public)
4,089
Tier-2 (your patterns)
private to your site
sse_transport
mcp-sse-transport-sseclienttransport-does-not-forward-custom-headers-9569721c
IFSSEClientTransport does not forward custom headers (including non-forbidden ones) on the initial /sse endpoint request.
THENModify the _startOrAuth method to merge headers from this._requestInit.headers into the fetch request for the /sse endpoint, similar to how send() does it. Ensure headers are included in the requestInit object passed to fetch.
Tier 170%
sse_transport
mcp-sse-transport-mcp-server-using-sse-transport-client-appends-mess-9d548e17
IFMCP server using SSE transport; client appends '/messages' to the endpoint obtained from /sse, causing 404 errors.
THENWhen implementing SSE transport in an MCP client, ensure the client uses the endpoint URL exactly as provided by the server in the /sse response. Do not assume the endpoint is <base>/messages. The client should store and reuse the endpoint for all subsequent requests. As SSE transport is deprecated, consider migrating to the streamable HTTP transport.
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