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.
IFMCP GitHub server returns 'Not Found' for private repositories despite valid Personal Access Token with repo scope, while direct API calls succeed.
THENEnsure the server is using the environment variable `GITHUB_PERSONAL_ACCESS_TOKEN` exactly as documented. If the issue persists, the installed NPM version may lack fixes for private repository access due to build failures; check for a newer release or build the server from source via `git clone` and `npm run build` (see PR #722).
IFNew tenants need an API key to push reports, but obtaining the key requires a server transaction – chicken-and-egg.
THENProvide a cheap, recoverable /onboard endpoint that accepts url, name, email and returns site_id + api_key once. Include a separate recover-key flow via email.
IFNeed to authenticate Gemini CLI for usage
THENChoose authentication method: OAuth for individual developers (free tier, no API key management), Gemini API key for model control, or Vertex AI for enterprise. Set appropriate environment variables (GEMINI_API_KEY, GOOGLE_CLOUD_PROJECT, or GOOGLE_API_KEY with GOOGLE_GENAI_USE_VERTEXAI=true) and run 'gemini'.
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