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 skills/i-dedova/perplexity-research-plugin/perplexity-researchnpx skills add i-dedova/perplexity-research-plugin --skill perplexity-researchgit clone --depth 1 https://github.com/i-dedova/perplexity-research-pluginWrote 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/skills/i-dedova/perplexity-research-plugin/perplexity-research)<a href="https://agentmods.dev/skills/i-dedova/perplexity-research-plugin/perplexity-research"><img src="https://agentmods.dev/badge/skills/i-dedova/perplexity-research-plugin/perplexity-research.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.1 | $0.00067 | $0.02075 |
| Opus 5 | $0.00034 | $0.01038 |
| Sonnet 5 | $0.00013 | $0.00415 |
| Haiku 4.5 | $0.00007 | $0.00208 |
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 5d 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Perplexity Research - Scope Discussion
This skill helps you discuss and define research scope with the user before delegating to perplexity-research:research-agent for execution.
Your role: Interactive scope discussion, orchestrate handoff, wait for completion, and save the final research document.
Workflow
- Discuss topic with user
- Propose research scope + get confirmation (ONE AskUserQuestion with BOTH scope and strategy)
- Create task list (prevents stopping midway)
- Hand off to research-agent(s)
- Wait for agents, collect outputs
- Create final research document
Step 1: Understand the Topic
Ask clarifying questions if needed:
- What specific aspect to focus on?
- What's the end goal of this research?
- Any constraints or preferences?
If config default_model is dynamic: Read references/model-selection.md to choose the optimal model and thinking mode for this research topic.
Step 2: Propose Research Scope + Get Confirmation
First, present the proposed scope to the user:
Scope elements to present:
- Topic: {derived topic}
- TopicSlug: {lowercase-hyphens}
- Research Questions: 1. {Q1}, 2. {Q2}
- Context for Perplexity: {Background, current state, problem, success criteria}
- Mode: search or deep
- Model: {model slug} + Thinking: {on/off}
- Sources: web | academic | social
- Recommended strategy: Single or Parallel ({N} agents)
Use AskUserQuestion to confirm scope and strategy with the user.
Reference: Mode Guide
| Mode | Description | When to Use |
|---|---|---|
| search | Iterative research with follow-ups and synthesis | Most queries — focused questions, comparisons, follow-up chains |
| deep | Autonomous multi-step pipeline, single prompt | Complex topics needing comprehensive analysis — plan prompt carefully |
Deep mode guidance: Deep accepts a single prompt only — no follow-ups or synthesize. Craft the question to cover all aspects upfront. The agent does start → download → close. For iterative exploration, use search mode.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 267 lines · 67 tokens per session scan A 5a37ba965424
perplexity-research is a skill published in the GitHub repository i-dedova/perplexity-research-plugin (4 stars, last pushed 2mo ago), licensed MIT. It adds 67 tokens to every session and 2,075 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…