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.
IFUsing mcpAuthRouter with an issuer URL that includes path segments (e.g., 'https://login.microsoftonline.com/TENANT_ID/v2.0') causes the automatic construction of authorization and token endpoints to strip away the path, resulting in broken endpoints like 'https://login.microsoftonline.com/authorize' instead of the correct URL.
THENOverride the OAuth metadata endpoints explicitly via the `authorizationOptions` and `tokenOptions` parameters (e.g., `authorizationEndpoint`, `tokenEndpoint`) to provide the full correct URLs. Alternatively, ensure the issuer URL ends with a trailing slash and configure endpoint constants without a leading slash so that URL concatenation preserves the path. For advanced scenarios, implement or use a `ProxyOAuthServerProvider` that accepts external endpoint URLs directly, as proposed in pull request #159.
IFWhen using mcpAuthRouter with an external OAuth provider whose issuer URL contains a path (e.g., https://login.microsoftonline.com/TENANT_ID/v2.0), the authorization endpoint is incorrectly constructed by dropping the path, leading to a 404 error.
THENEnsure the issuer URL ends with a trailing slash and that the endpoint constants (e.g., 'authorize') have no leading slash. Alternatively, manually override the authorization endpoint in the provider configuration to match the external provider's actual endpoint.
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