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/timurgaleev/memex/perplexity-researchnpx skills add timurgaleev/memex --skill perplexity-researchgit clone --depth 1 https://github.com/timurgaleev/memexWrote 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/timurgaleev/memex/perplexity-research)<a href="https://agentmods.dev/skills/timurgaleev/memex/perplexity-research"><img src="https://agentmods.dev/badge/skills/timurgaleev/memex/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 | $0.00104 | $0.01669 |
| Opus 5 | $0.00052 | $0.00834 |
| Sonnet 5 | $0.00021 | $0.00334 |
| Haiku 4.5 | $0.00010 | $0.00167 |
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 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.
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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
perplexity-research — Brain-Augmented Perplexity Research
Convention: see
conventions/quality.md(viaget_skill conventions/quality) for citation rules; every claim from Perplexity research lands with a verifiable citation, not a paraphrase.Convention: see
conventions/brain-first.md(viaget_skill conventions/brain-first) for the lookup chain. This skill ENFORCES brain-first by loading brain context BEFORE any web call — the web search focuses on the delta between brain knowledge and current web state.
What this does
Combines existing brain knowledge with the agent's web-search tooling. The agent first pulls what the brain already holds on a topic, then runs web searches and page reads framed by that context, synthesizing multiple sources with citations, focused on what's NEW relative to the brain.
The key insight: a research pass is only useful if it knows what you already know. By loading brain context first and searching against it, the output is the delta — not a re-narration of settled fact.
When to use this vs other tools
| Need | Use |
|---|---|
| Deep research with citations | This skill — brain context + web search + synthesis |
| Quick URL content | the agent's plain page-fetch tool |
| Brain-only lookup | search (MCP) / memex search |
| Real-time social monitoring | external social-media collectors |
| Structured data lookup against a tracker | skills/data-research/SKILL.md |
Output structure
The research output lands as a brain page under research/<slug> with
this structure:
---
title: "[Topic] — Research [YYYY-MM-DD]"
type: research
date: YYYY-MM-DD
brain_context_slugs: ["pages whose context framed the web pass"]
recency_filter: "[hour|day|week|month|none]"
---
# [Topic] — Research [YYYY-MM-DD]
> Executive summary: 2-3 sentences on the delta between brain knowledge
> and current web state.
## Key New Developments
What's changed since the brain was last updated on this topic.
## Confirming Signals
Web evidence validating existing brain knowledge.
## Contradictions or Updates
Things that conflict with the brain — these need a closer look.
## Recommended Brain Updates
Specific page updates the user might want to make based on this research.
Each item: which page, what to add or change, source URL.
## Citations
- [Source title](URL) — accessed YYYY-MM-DD
- [Source title](URL) — accessed YYYY-MM-DD
- ...
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.
- 4d ago First seen · 200 lines · 104 tokens per session scan A b854701760a8
perplexity-research is a skill published in the GitHub repository timurgaleev/memex (8 stars, last pushed 3d ago), licensed MIT. It adds 104 tokens to every session and 1,669 once invoked, about $0.0005 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
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
field-test
Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to…
api-config
Reference for core and server configuration in @cyanheads/mcp-ts-core. Covers env var tables with defaults, priority order, server-specific Zod schema pattern, and Workers lazy-parsing requirement.