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/cache-perplexity-sessiongit 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.01167 |
| Opus 5 | $0.00000 | $0.00583 |
| Sonnet 5 | $0.00000 | $0.00233 |
| Haiku 4.5 | $0.00000 | $0.00117 |
Grade B, and why
cache-perplexity-session scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Write to `~/.claude/config/perplexity-session.json`: How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cache-perplexity-session — Cache Perplexity Login for Council Commands
Capture Perplexity session state (cookies, localStorage, model preferences) from an already-authenticated browser session. Cached data is used by /council-refine and /export-to-council to skip fragile UI model-selector clicks.
Prerequisites: User must be logged into Perplexity in Chrome. Browser-bridge MCP server running with Chrome extension connected.
Input
$ARGUMENTS = Ignored (no arguments needed).
Workflow
Step 1: Navigate to Perplexity
browser_navigatetohttps://www.perplexity.ai/- Wait 3 seconds for full page load (auth state must be hydrated)
Step 2: Verify logged in
- Take a screenshot to confirm the user is logged in
- Look for indicators: user avatar, "New Thread" button, absence of "Sign in" button
- If NOT logged in, abort with message: "Please log into Perplexity in Chrome first, then re-run this command"
Step 3: Read session cookies
- Use
browser_evaluateto read cookies:document.cookie - Store the result as
cookiesstring
Step 4: Read localStorage preferences
- Use
browser_evaluateto read relevant localStorage keys:JSON.stringify(Object.fromEntries( Object.keys(localStorage) .filter(k => k.includes('session') || k.includes('model') || k.includes('user') || k.includes('auth') || k.includes('token') || k.includes('pplx') || k.includes('preference')) .map(k => [k, localStorage.getItem(k)]) )) - Parse the JSON result as
localStorageData
Step 5: Detect current model and council state
- IMPORTANT: Council is NOT in the model selector dropdown. It's a separate "Model council" button/chip in the input toolbar area.
- Use
browser_evaluateto check for the council button:(function() { const btn = [...document.querySelectorAll('button')].find(b => b.textContent.trim() === 'Model council'); const modelBtn = document.querySelector('button[aria-label="Choose a model"]'); const threeModels = document.querySelector('button[aria-label="3 models"]'); return { councilButton: btn ? { found: true, classes: btn.className, active: btn.className.includes('bg-subtle') } : { found: false }, modelSelector: modelBtn?.textContent?.trim() || 'not found', threeModelsDropdown: threeModels ? true : false }; })() - If council button found →
currentModel = "council" - If council button NOT found →
currentModel = modelSelector text
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 · 114 lines · 0 tokens per session scan B 8c8af9291a2e
cache-perplexity-session is a command published in the GitHub repository intellegix/intellegix-code-agent-toolkit (57 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,167 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
hep-browser
Use the Agentlas browser hardpoint for browser-required work.
agentlas-browser
Use the Agentlas browser hardpoint for browser-required work.
auto-verify
프론트엔드 UX 검증 — Playwright 기반 비주얼 검증을 실행합니다.
activate-browser
Activate Chrome DevTools MCP for heavy browser sessions (network inspection, Lighthouse, performance tracing). Deactivate when done.
dial
Live value calibration - 2-4 lettered candidates injected into the running app; click through them against real data, nothing written to source.
interactive-dev
Start a persistent interactive development session with natural language browser control, auto-error monitoring, and full dev tool access.