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.
git clone --depth 1 https://github.com/TechDufus/oh-my-claudeWrote 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/techdufus/oh-my-claude/prime)<a href="https://agentmods.dev/commands/techdufus/oh-my-claude/prime"><img src="https://agentmods.dev/badge/commands/techdufus/oh-my-claude/prime/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/techdufus/oh-my-claude/prime"><img src="https://agentmods.dev/badge/commands/techdufus/oh-my-claude/prime.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00020 | $0.02602 |
| Opus 5.5 | $0.00008 | $0.01041 |
| Sonnet 5.5 | $0.00004 | $0.00520 |
| Haiku 4.5 | $0.00002 | $0.00260 |
Grade A, and why
prime 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 1mo 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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/prime - Context Priming for Fresh Sessions
Rapidly build complete understanding of current work state after /clear or new session start. Uses parallel subagents to maximize context gathering while minimizing main context token usage.
Usage
/prime # Full context priming (default)
/prime <task-hint> # Prime with upcoming task focus
/prime --quick # Essential git state only (faster)
/prime --verbose # Include full diffs in report
Examples
/prime # General orientation
/prime migrating postgres init scripts # Focus exploration on postgres/init
/prime reviewing PR #42 # Pull PR context to forefront
Arguments: $ARGUMENTS
Philosophy
Problem: Fresh sessions lack context about in-progress work.
Solution: Subagents explore repository state in parallel, then synthesize into a concise briefing. Main context receives only the summary, not raw exploration data.
Task-Focused: When a task hint is provided, subagents prioritize context relevant to that task (pyramid approach - start with intent).
Phase -1: Parse Arguments
Parse $ARGUMENTS to extract:
- Task hint: Any non-flag text (e.g., "migrating postgres init scripts")
- Flags:
--quick,--verbose
Phase 0: Quick Snapshot (Main Agent)
Run these commands in parallel via Bash tool:
git branch --show-current
git rev-parse --abbrev-ref HEAD@{upstream} 2>/dev/null || echo "no upstream"
git status --short --branch
git log --oneline -5
git stash list --format="%gd: %s"
Display immediately:
## Quick Snapshot
- **Branch**: <current-branch> (tracking: <upstream-or-none>)
- **Status**: <N files changed, M staged, K untracked>
- **Recent commits**: <last 3-5 one-liners>
- **Stashes**: <count or "none">
If --quick flag provided, STOP HERE.
Subagent Prompt Template
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.
- 1mo ago First seen · 348 lines · 20 tokens per session scan A 4476d4b74319
prime is a command published in the GitHub repository TechDufus/oh-my-claude (174 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 2,602 once invoked, about $0.0001 per session on Opus 5.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
audit
Audit .flow/memory/ entries against the current codebase — Keep / Update / Consolidate / Replace / Delete / Harden per entry.
memory-migrate
Migrate legacy .flow/memory/{pitfalls,conventions,decisions}.md flat files into the categorized YAML schema — host agent classifies each entry directly.
memory
USE WHEN recalling past decisions, storing new insights, forgetting stale memories, linking memories, or reviewing pending memory proposals. Groups recall | learn (with optional --save-context) | forget | relate | propose.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
project
USE WHEN initializing a project goal, analyzing project context before starting work, or registering a project in the LTM registry. Groups init | analyze | register.
warden-select
Measure pending token-warden candidate rules for an agent on the golden suite, evict or activate them, and recompile the agent's memory.