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.
IFWhen using past_key_values with padded batches in GPT-2 (or similar causal language models), the default position_ids are computed incorrectly because past_length includes padding tokens, causing the logits of subsequent tokens to differ from a full forward pass.
THENManually specify correct position_ids for the new tokens, computed as the sequence lengths of each example before adding new tokens. Alternatively, use left-padding when tokenizing (tokenizer(padding_side='left')) so that padding does not disrupt position alignment.
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