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.
git clone --depth 1 https://github.com/intellegix/intellegix-code-agent-toolkitWrote 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/commands/intellegix/intellegix-code-agent-toolkit/solve-perplexity)<a href="https://agentmods.dev/commands/intellegix/intellegix-code-agent-toolkit/solve-perplexity"><img src="https://agentmods.dev/badge/commands/intellegix/intellegix-code-agent-toolkit/solve-perplexity/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/intellegix/intellegix-code-agent-toolkit/solve-perplexity"><img src="https://agentmods.dev/badge/commands/intellegix/intellegix-code-agent-toolkit/solve-perplexity.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.03234 |
| Opus 5.5 | $0.00000 | $0.01294 |
| Sonnet 5.5 | $0.00000 | $0.00647 |
| Haiku 4.5 | $0.00000 | $0.00323 |
Grade A, and why
solve-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 1mo 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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/solve-perplexity — Iterative Problem Solver via Perplexity
Iteratively solve complex bugs, edge cases, and nearly-unsolvable issues using progressive Perplexity queries with contradiction tracking and convergence detection. Tier 2.5 in the escalation ladder — between single-pass /research-perplexity (Tier 2) and user handoff (Tier 3).
Cost: $0 — uses Perplexity login session only (Playwright browser automation).
CRITICAL: This is a SOLVER, not a PLANNER. It outputs concrete fixes directly. Do NOT enter plan mode. Do NOT ask the user questions before completing Step 0 and Step 1. Compile context silently, decompose the problem, and begin iterating.
MANDATORY CONTEXT PREAMBLE — EVERY QUERY, NO EXCEPTIONS: Every single query sent to Perplexity 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]
When to Use
- Tier 2 (
/research-perplexity) returned low-confidence or contradictory results - Problem requires multiple angles of investigation (e.g., interplay between library version, OS, and config)
- Edge case that doesn't match any known pattern in docs or Stack Overflow
- Bug where root cause is ambiguous — multiple plausible hypotheses need systematic elimination
- Integration issues spanning multiple systems (API + DB + auth + deployment)
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.
- 1mo ago First seen · 309 lines · 0 tokens per session scan A 619ec09d05b7
solve-perplexity is a command published in the GitHub repository intellegix/intellegix-code-agent-toolkit (57 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,234 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
performance-optimization
Orchestrate end-to-end application performance optimization from profiling to monitoring.
refactor-clean
Refactor provided code for cleanliness, maintainability, and alignment with SOLID principles and modern best practices — no over-engineering.
config-validate
Validate application configuration with schemas, per-environment rules, runtime checks, and secure handling of sensitive values.
smart-debug
AI-assisted smart debugging — parse error messages, stack traces, and failure patterns to identify root causes and produce a fix with automated observability steps.
team-debug
Debug issues using competing hypotheses with parallel investigation by multiple agents.
recover-orphans
Scan for pipeline-orphaned issues stuck in intermediate workflow states and recover them — diagnose each orphan's actual GitHub state, apply recovery actions, clean up worktrees.