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.
IFSpawning a stdio MCP subprocess with custom environment variables fails with 'spawn npx ENOENT' or similar errors because default environment variables (HOME, PATH) are overwritten instead of merged.
THENMerge the default environment with custom environment variables when configuring the stdio transport. Use `env: { ...getDefaultEnvironment(), ...(this._serverParams.env ?? {}) }` to ensure critical system variables are preserved. If you cannot modify the SDK source, apply the merge manually before constructing the transport, as shown in the workaround: `serverParams.env = { ...getDefaultEnvironment(), ...serverParams.env }`.
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