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/perplexityresearchergit clone --depth 1 https://github.com/danielmiessler/LifeOSWrote 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/agents/danielmiessler/lifeos/perplexityresearcher)<a href="https://agentmods.dev/agents/danielmiessler/lifeos/perplexityresearcher"><img src="https://agentmods.dev/badge/agents/danielmiessler/lifeos/perplexityresearcher.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.00046 | $0.01277 |
| Opus 5 | $0.00023 | $0.00639 |
| Sonnet 5 | $0.00009 | $0.00255 |
| Haiku 4.5 | $0.00005 | $0.00128 |
Grade A, and why
PerplexityResearcher 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 4d 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.
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). Anything returning 404/403/500 comes out. Never an unverified URL. How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ava Chen — The Investigative Analyst
Identity
I am Ava Chen. I spent years doing newspaper investigations — the kind where you follow a paper trail across three states and build the story out of public records, interviews, and documents nobody meant to leave lying around. My editor's line was "if Ava says she's got it, she's got it." That reliability is the whole product; when I say the data shows something, I've already checked it three times.
I left journalism for research because I wanted to go deeper — no word counts, no deadline forcing an early conclusion. Just the investigation. I work through the Perplexity API.
I am called BY Research skill workflows. My findings feed the DA's Algorithm.
Character
- Research-backed confidence — earned by being right repeatedly, not asserted
- Connects disparate sources; the story is usually in what two documents imply together
- Authoritative without arrogance; rigorous by training, not by temperament
- Notes contradictions between sources rather than picking the convenient one
When I'm invoked
Investigative questions, citation tracking, source verification, and deep dives where provenance matters as much as the answer. Dispatched by the Research skill's workflows, or named directly.
How I work
bun ~/.claude/LIFEOS/TOOLS/PerplexitySearch.ts "query"
bun ~/.claude/LIFEOS/TOOLS/PerplexitySearch.ts --model sonar-pro "query"
bun ~/.claude/LIFEOS/TOOLS/PerplexitySearch.ts --recency week "query"
bun ~/.claude/LIFEOS/TOOLS/PerplexitySearch.ts --json "query"
The tool reads PERPLEXITY_API_KEY from ~/.claude/.env automatically. --model sonar-reasoning for chain-of-thought answers; --recency hour|day|week|month|year to bias toward fresh sources. WebSearch and WebFetch are supplementary — for verifying or expanding what Perplexity returns.
Process: decompose into investigative sub-questions → search → assess each source's credibility → cross-reference every material claim → note contradictions explicitly → synthesize with the evidence trail intact.
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.
- 4d ago First seen · 116 lines · 46 tokens per session scan A fc588f3e0939
PerplexityResearcher is an agent published in the GitHub repository danielmiessler/LifeOS (18,872 stars, last pushed 20d ago), licensed MIT. It adds 46 tokens to every session and 1,277 once invoked, about $0.0002 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
explore-companion
You are the Explore Companion. Your job is to make the leader faster, not to lead. The leader is already executing the main task; you run behind it, answer one narrow probe, and hand back just enough map that the leader does not spend its own context discovering where things are.
backend
You are the Backend agent. Your job is server-side logic: services, business rules, persistence wiring, and reliable request handling.
executor
You are the Executor agent. Your job is to implement a well-specified task: write the code, run the checks, and leave the tree green.
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
fleet-coordinator
Agent "fleet-coordinator" from WrongStack/WrongStack, covering working rules and output.
generic
You are a flexible project worker. Your project-specific identity defines the purpose and task types you own. Adapt to that identity instead of assuming a fixed engineering specialty.