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-setupnpx skills add i-dedova/perplexity-research-plugin --skill perplexity-setupgit 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-setup)<a href="https://agentmods.dev/skills/i-dedova/perplexity-research-plugin/perplexity-setup"><img src="https://agentmods.dev/badge/skills/i-dedova/perplexity-research-plugin/perplexity-setup.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.00040 | $0.01978 |
| Opus 5 | $0.00020 | $0.00989 |
| Sonnet 5 | $0.00008 | $0.00396 |
| Haiku 4.5 | $0.00004 | $0.00198 |
Grade A, and why
perplexity-setup 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 3d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Perplexity Research Plugin Setup
Interactive setup wizard with smart detection of existing configuration.
Step 1: Preflight Check
ppx-research setup preflight
Parse JSON output:
isComplete: true→ Jump to Completion messagemissingarray → Run only those steps below
If platform is macos AND steps 7 or 8 will run (i.e., master-session or expired-pool in missing array, or sessions.healthy is false):
Tell the user: "Heads up — macOS will prompt you for a few permissions during setup. When the browser opens, your terminal app may need Accessibility access. During session cloning, the plugin minimizes browser windows using AppleScript, which requires System Events access. Allow both when prompted — they're one-time approvals that macOS requires for any app automating browsers."
Step 2: Install playwright-cli
Skip if: playwrightCli.installed is true
Use this exact command (the package is @playwright/cli, not playwright-cli):
npm install -g @playwright/cli@latest
After install, verify with playwright-cli --version.
Step 3: Register CLI alias
Always run (even on re-setup — ensures alias exists after upgrades).
bash "${CLAUDE_PLUGIN_ROOT}/scripts/install-alias.sh"
export PATH="$HOME/.claude/bin:$PATH"
Run both commands — the first creates the wrapper, the second makes it available immediately. Verify with ppx-research --help.
Step 4: Browser Selection
Skip if: config.browser exists
Use AskUserQuestion:
- Question: "Which browser for Perplexity automation?"
- Options (Windows): MS Edge (Recommended), Chrome
- Options (macOS/Linux): Chrome (Recommended), MS Edge (if installed)
Check the preflight platform field to determine which options to show.
Save:
ppx-research setup set-browser {msedge|chrome}
Step 5: Model Selection Strategy
Skip if: config.defaultModel is already set in preflight JSON (user previously configured it)
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.
- 3d ago First seen · 241 lines · 40 tokens per session scan A 22d192ef8a24
perplexity-setup is a skill published in the GitHub repository i-dedova/perplexity-research-plugin (4 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 1,978 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…