Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/optimeta/paideia/reindexgit clone --depth 1 https://github.com/OPTIMETA/PAIDEIAWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/optimeta/paideia/reindex)<a href="https://agentmods.dev/commands/optimeta/paideia/reindex"><img src="https://agentmods.dev/badge/commands/optimeta/paideia/reindex.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00051 | $0.01750 |
| Opus 5 | $0.00026 | $0.00875 |
| Sonnet 5 | $0.00010 | $0.00350 |
| Haiku 4.5 | $0.00005 | $0.00175 |
Grade A, and why
reindex scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Output language
User-facing prose, status messages, and this command's narrative are rendered in $INTERFACE_LANG (from .course-meta). File paths, slash command names (/paideia:reindex), tier markers (🔥🔥/🔥/🟡/⚪), YAML keys, error_type values, and tool identifiers stay in English regardless of $INTERFACE_LANG.
What this does
Reindex answers one question: can this course's index artifacts be brought into conformance with current canonical vocabulary — without re-running /paideia:analyze?
Two jobs run in sequence:
(A) coverage.md — retired marker (do NOT emit these: ✅✅/✅/🔴/🔴🔴) → canonical rewrite
course-index/coverage.md may carry retired markers (✅✅/✅/🔴/🔴🔴) written by an older analyze run. Reindex rewrites them to the canonical vocabulary atomically:
retired (do NOT emit): ✅✅ → 🔥🔥 ✅ → 🔥 🔴🔴 → ⚪ 🔴 → 🟡
This mapping is the same normalization defined in commands/analyze.md Step 3 (analyze.md:301) and skills/course-builder/SKILL.md. Reindex is the analyze-free path to apply it.
Byte-preserving contract: substitution is scoped to the Exam-tier column and to non-pipe prose/legend lines (e.g. Legend: ✅ = high exam priority, Aggregate: 3 sections at ✅). Every other table cell — § numbers, section titles, HW coverage cell contents, ⚠weak flags — and the table header/separator rows are preserved byte-for-byte, even if a data cell happens to contain a retired glyph (e.g. a section title Checklist ✅ done). ⚠weak is never promoted or demoted. The Exam-tier column is located by the following priority order: (1) canonical Exam tier header (case-insensitive) — always wins; (2) non-canonical alias headers (Strength, Emphasis, Priority, Weight, Tier) — recognized when the canonical header is absent, fixing false-canonical exit-0 on Reverse-map tables that use an alias with a non-rightmost tier column; (3) headless fragment fallback — when no recognised header exists, the rightmost cell that actually carries a tier glyph (retired or canonical) is targeted, so a bare Notes/L2 trailing column with no glyph is never mistakenly rewritten.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 104 lines · 51 tokens per session scan A 8d20d6aa5ebb
reindex is a command published in the GitHub repository OPTIMETA/PAIDEIA (91 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,750 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
design-tutorial
Interactive guided tour of Naksha — learn commands through real exercises, discover workflows, and get oriented in under 10 minutes.
coding-drill
Rapid-fire reps — pattern recognition, complexity-of-this-snippet, template recall — flashcard cadence; prioritizes your weak patterns.
training-coach-trainer
Train-the-trainer (TtT) protocol for internal subject-matter-experts who will deliver a training program. Condensed adult-learning principles, facilitation skills, common SME-as-trainer failure modes, cohort facilitation practice schedule, and a TtT-readiness rubric. Refuses SME deployment without TtT.
training-measure-transfer
Kirkpatrick L3 (behavior) + L4 (results) measurement plan for a training program. Behavior observation protocol with sampling cadence, business-metric tracking, post-program reinforcement plan, redesign feedback loop. Refuses L1-only smile-sheet evaluation; refuses programs without baseline.
training-scenarios
Scenario / case library design for a skill domain — 10-15 scenarios across difficulty range with setup, decision points, response rubric, and debrief discussion guide. Format mirrors the structured-interview rubric pattern from the Hiring sub-system. Scenarios are the bridge from concept to on-job behavior; without…
case-practice
Mock case interview practice (McKinsey/BCG/Bain style).