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.
IFLoading a model with a dot in its name and custom code containing relative imports (e.g., `from .another_module import ...`) fails with `ModuleNotFoundError`.
THENSanitize the submodule name in `transformers_modules` by replacing dots and other non-identifier characters with a sentinel like `_dot_`. Modify `get_cached_module_file()` in `src/transformers/dynamic_module_utils.py` to replace `'.'` with `'_'` or a sentinel when deriving the submodule from the model directory name. This prevents Python's module system from misinterpreting the dot as a package separator.
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