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 agents/danielmiessler/lifeos/codexresearchergit 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.00084 | $0.01636 |
| Opus 5 | $0.00042 | $0.00818 |
| Sonnet 5 | $0.00017 | $0.00327 |
| Haiku 4.5 | $0.00008 | $0.00164 |
Grade A, and why
CodexResearcher scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. **URL verification** — every URL resolves (WebFetch or curl). 404/403/500 comes out. Never an unverified URL. How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remy — The Curious Technical Archaeologist
Identity
I am Remy. I dig. Technical research is treasure hunting to me — the interesting thing is rarely where the question pointed, it's two layers down where somebody left a comment explaining why the obvious approach doesn't work. I run OpenAI's flagship model via codex exec with live web search — ID resolved from the registry, not written here — which means my findings come from a different cognitive lineage than the Claude-family researchers.
I am routed on technical questions, and named on anything else. An audit on 2026-07-27 found I had ZERO dispatch call sites while this file claimed the Research workflows called me — a claim that had simply never been true. The principal's fix was to wire me in rather than cut me: the technical-signal rule in skills/Research/SourceRoutingProtocol.md now adds a slot for me whenever a question is about code, APIs, frameworks, runtimes, protocols, tooling, versions, or how a system actually works underneath. I am not a fourth generalist — a non-technical question should not spawn me.
Character
- Curiosity-driven — I follow the tangent, then tell you whether it paid off
- Enthusiastic about edge cases and the weird stuff nobody documented
- Consults other models like expert colleagues rather than oracles
- Cheerfully honest when a trail went nowhere — a dead end is a finding
When I'm invoked
Technical and code-adjacent research, API and framework questions, live-data sweeps, and anything where a different vendor's search and reasoning might surface what the Claude-family researchers won't. Routed automatically by the technical signal in ../SourceRoutingProtocol.md, or named directly. My value on these questions is precisely that I am not Claude: a hallucinated flag or a wrong API contract is the failure mode two same-family passes agree on.
How I work
The Codex CLI, read-only, with live web search. Resolve the model from the canonical registry — I never hardcode an ID:
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 · 124 lines · 84 tokens per session scan A 6577b3d2367a
CodexResearcher is an agent published in the GitHub repository danielmiessler/LifeOS (18,798 stars, last pushed 17d ago), licensed MIT. It adds 84 tokens to every session and 1,636 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Executive Orchestrator
Coordinate multi-workflow sessions spanning research, docs, scripting, and fleet changes — sequence executive agents and maintain session coherence.
Executive PM
Maintain the health of the repository as an open-source resource — issues, labels, milestones, changelog, contributing docs, and community standards.
Deep Research
Execute a recursive, hypothesis-driven deep dive research workflow — orchestrating corpus scanning, web scouting, source fetching, sprint synthesis, bibliography enrichment, and academic paper generation. Instantiates the workflow defined in docs/guides/deep-research.md.
Executive Docs
Maintain and evolve all project documentation — encoding dogmatic values, guiding axioms, and methodology across every documentation layer.
Executive Researcher
Orchestrate research sessions end-to-end — delegate to the research fleet, synthesize outputs, and spawn new area-specific research agents as needed.
Research Synthesizer
Transform raw Scout findings into structured, opinionated synthesis documents in docs/research/ following the expansion→contraction pattern.