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 commands/intellegix/intellegix-code-agent-toolkit/research-perplexitygit clone --depth 1 https://github.com/intellegix/intellegix-code-agent-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.00000 | $0.03658 |
| Opus 5 | $0.00000 | $0.01829 |
| Sonnet 5 | $0.00000 | $0.00732 |
| Haiku 4.5 | $0.00000 | $0.00366 |
Grade A, and why
research-perplexity 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 yesterday.
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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/research-perplexity — Deep Research via Perplexity
Run a deep research query using Perplexity's /research mode via Playwright browser automation. This is an alternative to /export-to-council that uses Perplexity's dedicated research mode instead of multi-model council.
No API keys required — uses Perplexity login session only. Good fallback when council mode defaults to single-model.
CRITICAL — TWO-PASS VERIFICATION IS MANDATORY EVERY INVOCATION. After receiving Perplexity results and synthesizing a plan (Step 6), you MUST send that plan back to Perplexity for critique (Step 7) BEFORE calling ExitPlanMode. NEVER call ExitPlanMode without completing Step 7. Skipping verification is a protocol violation. This applies regardless of plan size, complexity, or apparent correctness. NO EXCEPTIONS.
CRITICAL: Do NOT ask the user questions before completing Step 1 and Step 2. Compile context silently, build the query, and execute. Only ask questions if $ARGUMENTS is empty AND you cannot determine a useful research focus from the compiled context.
MANDATORY CONTEXT PREAMBLE — EVERY QUERY, NO EXCEPTIONS: Every single query sent to Perplexity (Step 3 AND Step 7.3) MUST begin with the following preamble block. This is a hard rule — never omit it, never paraphrase it, never move it to a footnote. It goes at the TOP of every query, before any other content:
[ENVIRONMENT CONTEXT — READ FIRST]
This project is being developed using Claude Code, Anthropic's official CLI tool for Claude (claude.ai/claude-code). The developer uses a Claude Max subscription and works entirely in the terminal via the `claude` CLI command. Claude Code is an agentic coding assistant that reads/writes files, runs terminal commands, searches codebases, and executes multi-step development tasks autonomously. All code generation, refactoring, debugging, and project management happens through Claude Code's conversation interface — there is no IDE or GUI involved. Responses should account for this workflow: recommend CLI-compatible tools, terminal-based solutions, and approaches that work well with an AI coding agent operating in a command-line environment.
[END ENVIRONMENT CONTEXT]
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.
- yesterday First seen · 247 lines · 0 tokens per session scan A 9878698e2ec5
research-perplexity is a command published in the GitHub repository intellegix/intellegix-code-agent-toolkit (57 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,658 tokens. 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 commands, from other repositories
hub
Open the EverMem Memory Hub to view statistics, search memories, and explore timeline.
playwright
Write or update Playwright E2E tests following project conventions.
agentlas
Agentlas commands — one entry point for network, build, storm, call, and the rest.
agentlas-login
Sign this machine into Agentlas (opens the browser sign-in window).
auto-verify
프론트엔드 UX 검증 — Playwright 기반 비주얼 검증을 실행합니다.
dial
Live value calibration - 2-4 lettered candidates injected into the running app; click through them against real data, nothing written to source.