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.
IFLogged loss is not divided by gradient accumulation steps, resulting in an incorrectly large reported loss when gradient accumulation is used.
THENModify the `_maybe_log_save_evaluate` method to accept the number of gradient accumulation steps (`ga_steps`). When computing the logged loss, divide `tr_loss_scalar` by `ga_steps` before dividing by the number of steps since last log. This ensures the reported loss accurately reflects the per-step loss rather than the accumulated loss over multiple gradient accumulation steps.
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