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.
IFUsers are unsure when BOS tokens are added by vLLM, leading to double BOS tokens.
THENDocument that for non-chat APIs (offline generate, online completion) BOS is forced, so input prompts should not include BOS; for chat APIs, BOS is typically part of the chat template, so users should not add it manually.
IFNeed to set up integration between TrendRadar and OpenClaw.
THENProvide a minimal example showing the cron configuration, the command to execute (e.g., python main.py --mode push), expected output format, recommended timeout, and troubleshooting steps.
IFLLMs fail to import and use the MCP TypeScript SDK due to .js imports and lack of tsconfig.json guidance in README.
THENInclude a recommended tsconfig.json configuration in the README that sets proper module resolution (e.g., module: 'node16', moduleResolution: 'node16') and enables ES module interop, so that LLMs can correctly set up a TypeScript project to import the package.
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