Greek marks mood mostly by ending, not by word order or an auxiliary verb the way English uses “do” or “let”. In most persons the imperative ending is distinct from the indicative. But in the 2nd person plural, present tense, the two moods are true homographs — ζητεῖτε is spelled and accented identically whether Rav Shaul is reporting that you seek or ordering you to. Only the discourse context (a conditional clause stating a completed fact, followed by a string of commands) tells you which one you’re reading. This page gathers every imperative in the Jewish Greek Brit Chadasha and flags the 444 that fall in that ambiguous 2nd-plural-present zone with an ≈IND badge, so the “hidden commands” are easy to find.
Because in Greek, the command is not added to the verb — it is built into it. English marks the imperative by subtraction: drop the subject, use the bare stem, and hope word order and tone carry the rest (“Seek!” looks and sounds nothing like a distinct grammatical form — it’s just the dictionary form standing alone). Greek does the opposite. Mood is a formal category with its own dedicated endings — -ε, -ετε, -σον, -σατε, -σθω, -σθε, -τω, -τωσαν and the rest — woven into the sound-pattern of the word itself. A Greek imperative doesn’t sound like a statement that you’re supposed to read as a command; in almost every person and number, it is phonemically distinct from the indicative the instant you hear it spoken. The 2nd-plural present is the one narrow exception — which is precisely why Colossians 3:1–2 needs a trained eye rather than an ear.
Greek commands also carry a layer of precision most modern languages simply have no slot for: aspect. A present-tense imperative (ζητεῖτε, “keep seeking”) orders an ongoing, habitual posture; an aorist imperative (ζήτησον, “seek it”) orders a decisive, once-for-all act. English “seek” can mean either, and you cannot tell which without extra words. The Greek verb tells you by its ending alone whether the Master is asking for a lifelong habit or a single decisive break. Translating that distinction faithfully — without flattening every command into the same generic “you should” — is exactly the kind of precision this Marching Orders grid is built to preserve.
And these really are orders, not suggestions offered for consideration. In an army, disobeying a direct order carries real teeth — court martial, reduction in rank, dishonorable discharge. Scripture itself reaches for that same register: the believer is called a good soldier of Messiah Yeshua (2 Tim 2:3–4), armed for battle (Eph 6:10–17), enlisted under a Commander whose rhema is not offered as commentary but issued as command. The consequences for ignoring these 444 present-tense marching orders and the 1,645 imperatives surrounding them are not a court martial or a discharge paper — they are quieter and, in their own way, more costly: a cooling of first love, a drifting back into the old patterns Colossians 3 tells you to put to death, a conscience that stops answering when the Spirit speaks. Backsliding is what disobeyed marching orders look like in the life of a believer. That is reason enough to know exactly which sentences in your Bible are commands — and this page exists so you never again have to guess.
Source data. Every word of the Jewish Greek Brit Chadasha (across NA27/28, TR, SBL, WH, Treg, Byz, and THGNT) comes tagged with a Robinson-style morphology code from the STEPBible TAGNT (Translators Amalgamated Greek New Testament), a project of Tyndale House, Cambridge, released Creative Commons BY 4.0 on GitHub at github.com/STEPBible/STEPBible-Data. Each verb carries a code like V-PAM-2P (Verb–Present–Active–iMperative–2nd–Plural). The mood is scholarly-assigned per occurrence — so ζητεῖτε in Col 3:1 is already correctly tagged V-PAM-2P, not V-PAI-2P, because the Tyndale team resolved the ambiguity by hand from context, exactly as a good commentary would.
Why Python and not a Bible-software search. Most Bible tools let you search by lemma (dictionary form of the word) or by Strong’s number, but few let you search by mood across the whole NT and export the results as data. Because the TAGNT files are plain tab-separated text, they're easy to parse directly:
import re
row_re = re.compile(r'^([A-Za-z0-9]+)\.(\d+)\.(\d+)#(\d+)=')
parse_re = re.compile(r'=(V-\S+)')
# for each line: match reference, pull the code after "=V-", check
# whether the 3rd letter of the Tense-Voice-Mood block is "M" (Robinson mood letters:
# I=Indicative, S=Subjunctive, O=Optative, M=iMperative, N=Infinitive, P=Participle)
The companion legend file TEGMC (Translators Expansion of Greek Morphology Codes), also in the STEPBible-Data repo, spells every code out in full (“Verb Present Active Imperative 2nd Plural”), so codes don’t need to be decoded by hand.
What counts as “ambiguous.” Only 2nd-plural present-tense imperatives are flagged here, because that is the one cell in the paradigm where the ending is identical to the indicative in both active and middle/passive conjugations. Aorist imperatives are distinguished from aorist indicatives by the augment (indicative ἐποιήσατε vs. imperative ποιήσατε), and 2nd-singular present forms differ too (indicative ζητεῖς vs. imperative ζήτει). The 2nd-plural present is the one true blind spot — and it is exactly where Colossians 3:1–2, Philippians 4:4–6, and a number of other well-known “marching orders” sit.
On GitHub already. Besides STEPBible-Data itself, the awesome-bible-developer-resources list rounds up comparable tagged texts (MorphGNT/SBLGNT, unfoldingWord’s UGNT, Tischendorf 8th ed.) if you ever want to cross-check STEPBible’s mood-tagging against an independent parser — genuine ambiguities are rare enough in the manuscript tradition that the editions agree almost everywhere.