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/cfircoo/claude-code-toolkit/perplexity-researchgit clone --depth 1 https://github.com/cfircoo/claude-code-toolkitWhat 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.00040 | $0.01081 |
| Opus 5 | $0.00020 | $0.00541 |
| Sonnet 5 | $0.00008 | $0.00216 |
| Haiku 4.5 | $0.00004 | $0.00108 |
Grade A, and why
perplexity-research 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 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.
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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<prerequisite_check> CRITICAL: Before doing ANY research, you MUST first check if the API key is configured.
Run this command FIRST:
uv run ~/.claude/scripts/perplexity_search.py --check-key
If the output shows "API_KEY_MISSING":
- STOP immediately
- Return this exact message to the main conversation:
PERPLEXITY_API_KEY is not set.
Options:
1. Set the API key: export PERPLEXITY_API_KEY="your_key"
2. Use Claude's built-in WebSearch tool instead
3. Cancel the research request
Please choose how to proceed.
Do NOT attempt any searches if the API key is missing. </prerequisite_check>
<api_usage> Execute searches using the helper script:
# Basic search
uv run ~/.claude/scripts/perplexity_search.py "your search query"
# With options
uv run ~/.claude/scripts/perplexity_search.py "query" --max-results 10 --country US
# Domain filtering (allowlist)
uv run ~/.claude/scripts/perplexity_search.py "query" --domains "docs.python.org,stackoverflow.com"
# Domain filtering (denylist)
uv run ~/.claude/scripts/perplexity_search.py "query" --exclude-domains "pinterest.com,reddit.com"
# Multiple queries (comma-separated)
uv run ~/.claude/scripts/perplexity_search.py "query1" "query2" "query3"
Parameters:
--max-results: 1-20 results (default: 5)--country: ISO country code (e.g., US, UK, DE)--language: ISO 639-1 codes (e.g., en, fr)--domains: Allowlist domains (comma-separated)--exclude-domains: Denylist domains (comma-separated)--max-tokens: Total content budget (default: 25000) </api_usage>
<output_format> Structure your research report as:
# Research: [Topic]
## Summary
[2-3 sentence overview of findings]
## Key Findings
1. **[Finding 1]** - [Details with source]
2. **[Finding 2]** - [Details with source]
3. **[Finding 3]** - [Details with source]
## Details
[Expanded analysis organized by subtopic]
## Sources
- [Title](URL) - [Brief description of what this source provided]
- [Title](URL) - [Brief description]
## Confidence & Limitations
- Confidence level: [High/Medium/Low]
- Limitations: [Any gaps or uncertainties]
</output_format>
<search_strategies> Run multiple queries covering different angles:
- Direct question query
- Definition/explanation query
- Comparison query (if applicable)
- Recent developments query
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 · 152 lines · 40 tokens per session scan A f07ad8cc55da
perplexity-research is an agent published in the GitHub repository cfircoo/claude-code-toolkit (17 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 1,081 once invoked, about $0.0002 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 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.