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/danielmiessler/lifeos/context-searchgit clone --depth 1 https://github.com/danielmiessler/LifeOSWhat 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.00052 | $0.00114 |
| Opus 5 | $0.00026 | $0.00057 |
| Sonnet 5 | $0.00010 | $0.00023 |
| Haiku 4.5 | $0.00005 | $0.00011 |
Grade A, and why
Context Search 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 yesterday.
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.
What it actually says
Context Search — Redirect
Thin invoker for the Cortex skill's recall workflow (sessions, ISAs, conversations by topic or date phrase).
Skill("Cortex", "recall $ARGUMENTS")
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.
- yesterday First seen · 14 lines · 52 tokens per session scan A cde97f4d698d
Context Search is a command published in the GitHub repository danielmiessler/LifeOS (18,798 stars, last pushed 17d ago), licensed MIT. It adds 52 tokens to every session and 114 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
run
Execute seed spec via Double Diamond (Discover → Define → Design → Deliver). USE AFTER /decompose. Enforces D→L→P implementation order, writes tests immediately, runs gates continuously. Supports Pair Mode for medium/high complexity ACs.
evaluate
Run 3-stage verification (Mechanical gates → Semantic AC compliance → Judgment quality) after /run. ALWAYS run before committing. Blocks at Stage 1 failures — no Stage 2 until gates pass.
observe
Define observability spec (metrics/logs/traces) for a target before implementation. Provided by the Observability First methodology.
rfc
Manage RFCs — design review for high-stakes changes before code. Provided by the RFC-driven methodology.
methodology
Methodology plugin manager. List, activate, compose, deactivate development methodologies (Ouroboros, Living Spec, Parallel Change, BMAD-lite, Exploration). Harness gates remain enforced regardless of methodology.
spike
Create or manage time-boxed spikes (research investigations) with sandbox exempt from spec/boundary gates. Provided by the Exploration methodology.