Every Commander player has a deck with a passenger in it: a card that looked right, got sleeved two years ago, and has not mattered in a game since.
Finding those cards by playing is slow; you notice a dead draw once a night, shrug, and forget by the next game. Reading the list card by card is not much better, because each card looks reasonable alone. The problem is never the card, it is the relationship between the card and the other ninety-nine. That relationship is exactly what a paste-import audit checks, and it costs about thirty seconds. Here is the whole process.
Step 1: Export your decklist
Copy your list as plain text from wherever it lives:
- Moxfield: open the deck, use Export, copy the text list.
- Archidekt: deck menu, Export, text format.
- EDHREC: copy a decklist straight off any deck page.
- MTGO: the .txt export works as-is.
- Anything else: a plain list of card names, one per line, with or without quantities, is enough.
There is no format picker in Deckaugur. The importer reads all of these automatically, including the commander line.
Step 2: Paste it in
Open the workbench, choose the paste-import, and paste. The deck loads with your commander in place, and the synergy engine reads every card's oracle text against every other card. Nothing needs to be re-entered by hand, and your original list is untouched wherever it lives; this is a copy for analysis.
Step 3: Read the warnings first
Start at the panel called SOMETHING TO RECONSIDER. These are cards whose conditions your deck never actually meets: the spellslinger payoff in a deck running six instants, the token doubler in a deck that makes no tokens. Each warning explains which requirement is unmet, and where the engine knows a better fit for your themes it offers a replacement. This panel is the fastest honest answer to the question you brought here: which cards are not pulling their weight.
Step 4: Check the StarMap for orphans
Open the StarMap and the deck becomes a graph: every card a node, every synergy a line. You are looking for two things. Tight clusters are your engines, the parts of the deck that actually win games; it is worth knowing what they are so you protect them when trimming. And nodes floating alone at the edge are cards with no relationships at all. A lone node is not always a cut (removal and ramp can legitimately stand alone), but a lone node you cannot explain usually is.
Step 5: Mine the suggestions
WHISPERS FROM THE LIBRARY ranks cards from the full pool that fit the themes your deck actually has, not the themes a statistics site assumes for your commander. Suggestions only score highly when the deck both produces an effect and rewards it, so what surfaces here tends to be specific to your build. Two refinements worth knowing:
- If you have imported your collection, the owned-only filter restricts suggestions to cards already in your binder: free upgrades first.
- Clicking any tag pill on a card filters the suggestions to that theme, which is the quickest way to deepen the part of the deck that is working.
What to do with the verdict
A sensible audit ends with three small lists: cards to cut (warnings plus unexplained orphans), cards to add (top suggestions, owned first), and the engine clusters to leave alone. Make the swaps, watch the grade and the map respond, and export the shopping list for anything you do not own; it comes with prices in your preferred marketplace. Then take the deck back to your table, because the final judge is still the game. If the engine got a card wrong, flag it from the workbench; corrections feed the tag dictionary and the next audit gets sharper.
Your canonical list can stay on Moxfield or Archidekt; the audit is never more than a paste away.
Further reading
- How synergy scoring works: what the score measures, how suggestions earn their rank, and why warnings fire.
- The Commander Deckbuilder Guide: how EDHREC, Moxfield and Archidekt work, and where Deckaugur fits among them.
- Why your deck is missing removal: how interaction erodes out of a deck, and how much is enough.