Commander Intelligence

Ruby, Daring Tracker - Combos & Interactions

Verified sequences, reviewed requirements, interruption points, and rules notes.

Combo Summary

Reviewed lines to check

Verified combos1Reviewed interactions0Commander-required1Last reviewedJul 19, 2026

Combos & Interactions

Requirements and sequence

These are reviewed gameplay relationships, not a decklist and not proof that a card is moving in the market.

1 lines

Infinite

Ruby, Bard Class, Agatha, and Kogla loop

Verified

Infinite enters-the-battlefield events, infinite leaves-the-battlefield events, infinite storm count, and Bard Class level-3 exile access. A payoff is still required to turn the loop into a win.

Required Cards

Setup

  • Ruby is in hand or in the command zone.
  • Bard Class is on the battlefield at level 2 or higher.
  • Agatha of the Vile Cauldron and Kogla, the Titan Ape are on the battlefield.
  • Bard Class and commander tax math currently let Ruby be cast for {0}.
  • Agatha's reduction makes Kogla's activated ability cost {G}.

Ruby must cost {0}; Ruby's own {G} pays the reduced Kogla return activation.

Sequence

  1. Cast Ruby from hand or command zone for {0}.
  2. Tap Ruby for {G}.
  3. Pay {G} to activate Kogla and return Ruby to your hand.
  4. Repeat the cast, tap, and return sequence.
  5. If Bard Class is level 3, use the repeated legendary casts to exile cards from your library with play permission.

Interruption Points

  • Remove or counter Ruby before she can tap.
  • Remove Bard Class or lower the cost-reduction setup before Ruby is cast.
  • Remove Agatha before Kogla's activated ability is reduced.
  • Remove or disable Kogla before the return activation.
  • Apply commander tax beyond the available reduction.
  • Use Cursed Totem, Collector Ouphe-style restrictions where applicable, or instant-speed removal before the loop repeats.

Ruby, Daring Tracker role: Ruby is the zero-cost legendary spell and green mana source that pays the reduced Kogla activation.

Timing: Ruby must be able to tap after entering.

Rules notes: This record is the Gruul-legal Commander Spellbook combo 2092-2246-3657-6726. The loop makes ETB, LTB, and storm count but does not itself deal damage or make mana beyond the repeated payment. Bard Class level 3 can exile the library with play permission, but a castable payoff is still required. Temur Sabertooth, Heartstone, and Kogla variants must be reviewed as separate records. Zirda, Training Grounds, and Biomancer's Familiar variants are rejected for Ruby because they add off-color identity. Ruby rule 1: Ruby has haste, so she can attack and use her tap ability as soon as she comes under your control. Ruby rule 2: Ruby's attack trigger checks whether you control a creature with power 4 or greater as Ruby is declared attacking. Ruby rule 3: Ruby counts herself only if her power is already 4 or greater before attackers are declared. Ruby rule 4: Removing or shrinking the qualifying power-4 creature after the ability triggers does not stop the +2/+2 bonus. Ruby rule 5: The attack trigger resolves before blockers are declared. Ruby rule 6: Extra combat phases can trigger Ruby again if she attacks again and the power-4 condition is true. Ruby rule 7: Ruby's mana ability is a mana ability and does not use the stack. Ruby rule 8: Commander tax can break Bard Class loops unless the cost reduction and return-to-hand sequence account for it. Ruby rule 9: Bard Class level 2 reduces the cost of legendary spells; level 3 adds the exile-and-play permission during the loop. Ruby rule 10: Agatha of the Vile Cauldron reduces activated abilities of creatures you control based on Agatha's power, but it does not make illegal off-color cards legal. Ruby rule 11: Kogla and Temur Sabertooth variants require separate bounce costs and board states. Ruby rule 12: Cascade deckbuilding can constrain low-cost interaction because cascade cares about mana value.

Last reviewed: Jul 19, 2026

Card Intelligence

Exact cards to compare

Open card pages for exact printing, NeoPrice, Pricing Confidence, CardTrader inventory, seller depth, and version checks.

Market caution

A verified combo explains a gameplay relationship. It does not prove that the combo is causing current price or inventory movement. Compare exact printing, condition, finish, seller depth, marketplace agreement, and Pricing Confidence separately.

Next Checks

Where to go next