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.
IFWhen using `mcpAuthRouter` with a `baseUrl` that includes a path (e.g., `/auth`), the generated OAuth metadata endpoints use absolute paths, ignoring the baseUrl path.
THENEnsure that the `createOAuthMetadata` function prepends the baseUrl's pathname to the OAuth endpoints (authorize, token, etc.). For example, if baseUrl is `https://example.com/auth`, endpoints should be `/auth/authorize` and `/auth/token`. If using a fork or patched version, modify the metadata generation to use `new URL('authorize', baseUrl)` or similar logic.
IFWhen using mcpAuthRouter with a baseUrl that includes a path component (e.g., '/auth'), the generated OAuth metadata endpoints omit the path prefix.
THENModify the OAuth metadata generation to prepend the baseUrl path to endpoint URLs, e.g., by resolving relative paths against the baseUrl (e.g., new URL('authorize', baseUrl).href) instead of using absolute paths.
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