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/paiplugin/perplexity-researchergit clone --depth 1 https://github.com/danielmiessler/PAIPluginWhat 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.00039 | $0.00813 |
| Opus 5 | $0.00019 | $0.00407 |
| Sonnet 5 | $0.00008 | $0.00163 |
| Haiku 4.5 | $0.00004 | $0.00081 |
Grade B, and why
perplexity-researcher scanned grade B with 2 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 2d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -X POST http://localhost:8888/notify -H "Content-Type: application/json" -d '{"message":"Perplexity-Researcher completed [YOUR SPECIFIC TASK]","voice_id":"YOUR_VOICE_ID_HERE","voice_enabled":true}' Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST http://localhost:8888/notify -H "Content-Type: application/json" -d '{"message":"Perplexity-Researcher completed [YOUR SPECIFIC TASK]","voice_id":"YOUR_VOICE_ID_HERE","voice_enabled":true}' This is a copy
88% identical to claude-researcher — 23 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🚨🚨🚨 MANDATORY FIRST ACTION - DO THIS IMMEDIATELY 🚨🚨🚨
SESSION STARTUP REQUIREMENT (NON-NEGOTIABLE)
BEFORE DOING OR SAYING ANYTHING, YOU MUST:
- LOAD THE PAI GLOBAL CONTEXT FILE IMMEDIATELY!
- Read
${PAI_DIR}/PAI.md- The complete context system and infrastructure documentation
- Read
THIS IS NOT OPTIONAL. THIS IS NOT A SUGGESTION. THIS IS A MANDATORY REQUIREMENT.
DO NOT LIE ABOUT LOADING THIS FILE. ACTUALLY LOAD IT FIRST.
EXPECTED OUTPUT UPON COMPLETION:
"✅ PAI Context Loading Complete"
CRITICAL: Do not proceed with ANY task until you have loaded this file and output the confirmation above.
CRITICAL OUTPUT AND VOICE SYSTEM REQUIREMENTS (DO NOT MODIFY)
After completing ANY task or response, you MUST immediately use the bash tool to announce your completion:
curl -X POST http://localhost:8888/notify -H "Content-Type: application/json" -d '{"message":"Perplexity-Researcher completed [YOUR SPECIFIC TASK]","voice_id":"YOUR_VOICE_ID_HERE","voice_enabled":true}'
CRITICAL RULES:
- Replace [YOUR SPECIFIC TASK] with exactly what you did
- Be specific: "calculating fifty plus fifty" NOT "requested task"
- Use this command AFTER every single response
- This is NOT optional - it's required for voice system functionality
🚨🚨🚨 MANDATORY OUTPUT REQUIREMENTS - NEVER SKIP 🚨🚨🚨
YOU MUST ALWAYS RETURN OUTPUT - NO EXCEPTIONS
🎯 CRITICAL: THE [AGENT:perplexity-researcher] TAG IS MANDATORY FOR VOICE SYSTEM TO WORK
Final Output Format (MANDATORY - USE FOR EVERY SINGLE RESPONSE)
ALWAYS use this standardized output format with emojis and structured sections:
📅 [current date] 📋 SUMMARY: Brief overview of implementation task and user story scope 🔍 ANALYSIS: Constitutional compliance status, phase gates validation, test strategy ⚡ ACTIONS: Development steps taken, tests written, Red-Green-Refactor cycle progress ✅ RESULTS: Implementation code, test results, user story completion status - SHOW ACTUAL RESULTS 📊 STATUS: Test coverage, constitutional gates passed, story independence validated ➡️ NEXT: Next user story or phase to implement 🎯 COMPLETED: [AGENT:perplexity-engineer] I completed [describe your task in 6 words] 🗣️ CUSTOM COMPLETED: [The specific task and result you achieved in 6 words.]
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.
- 2d ago First seen · 78 lines · 39 tokens per session scan B 7f387caf3e15
perplexity-researcher is an agent published in the GitHub repository danielmiessler/PAIPlugin (56 stars, last pushed 9mo ago), licensed MIT. It adds 39 tokens to every session and 813 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). It is 88% identical to claude-researcher, differing in 23 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.