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/raken-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.03587 |
| Opus 5 | $0.00000 | $0.01793 |
| Sonnet 5 | $0.00000 | $0.00717 |
| Haiku 4.5 | $0.00000 | $0.00359 |
Grade A, and why
raken-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 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 — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/raken-perplexity — Raken API Research-Grounded Implementation via Perplexity
Run a Raken API-focused research query using Perplexity's research mode. Every query is grounded in the actual Raken Public API 3.0 documentation — endpoints, OAuth flow, response schemas, rate limits, and existing integration scripts are loaded and injected as mandatory context before any research or implementation planning begins.
MANDATORY: You MUST read the Raken API documentation directory BEFORE building any query, designing any approach, or planning any implementation. Skipping the documentation read is a protocol violation. NO EXCEPTIONS.
CRITICAL — TWO-PASS VERIFICATION IS MANDATORY EVERY INVOCATION. After receiving Perplexity results and synthesizing a plan (Step 5), you MUST send that plan back to Perplexity for critique (Step 6) BEFORE calling ExitPlanMode. NEVER call ExitPlanMode without completing Step 6. Skipping verification is a protocol violation. NO EXCEPTIONS.
CRITICAL: Do NOT ask the user questions before completing Step 0 through Step 1. 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 2 AND Step 6.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.
- 3d ago First seen · 296 lines · 0 tokens per session scan A c1a97382b480
raken-perplexity 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 3,587 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
README
Git workflow and quality assurance commands for the claude-skills repository.
loop
Iteratively fix issues until all resolved or max iterations reached.
OpenSpec: Apply
Implement an approved OpenSpec change and keep tasks in sync.
auto-goal
goal 래퍼 — /goal 생성, 상태 확인, 완료/blocked handoff를 goal tool 또는 slash command로 연결합니다.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
implement-task
根据技术方案实施任务并输出实现报告.