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
1
Categories
2258
Tier-1 (public)
4,089
Tier-2 (your patterns)
private to your site
sso_oauth_redirection
security-sso-oauth-redirectio-gitlab-sso-login-redirects-to-public-gitlab-com-in-c76a9c50
IFGitLab SSO login redirects to public gitlab.com instead of the configured custom GitLab domain (e.g., gitlab.company.com).
THENExplicitly set the authorization URL in the GitLabProvider configuration. Add an environment variable (e.g., AUTH_GITLAB_AUTH_URL) and use it to construct the authorization endpoint. For example: `authorization: { url: process.env.AUTH_GITLAB_AUTH_URL, params: { scope: 'read_user' } }`. This ensures the redirect goes to the correct custom GitLab instance.
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