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/export-to-councilgit 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/export-to-council)<a href="https://agentmods.dev/commands/intellegix/intellegix-code-agent-toolkit/export-to-council"><img src="https://agentmods.dev/badge/commands/intellegix/intellegix-code-agent-toolkit/export-to-council.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.00000 | $0.02269 |
| Opus 5 | $0.00000 | $0.01135 |
| Sonnet 5 | $0.00000 | $0.00454 |
| Haiku 4.5 | $0.00000 | $0.00227 |
Grade A, and why
export-to-council 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/export-to-council — Export Session to Multi-Model Council Analysis
Query 3 frontier AI models (GPT-5.2, Claude Sonnet 4.5, Gemini 3 Pro) via Perplexity API or browser automation, then synthesize findings. Automatically enters plan mode to study implementation.
No API keys required for browser mode — uses Perplexity login session. API mode requires PERPLEXITY_API_KEY + ANTHROPIC_API_KEY.
CRITICAL: Do NOT ask the user questions before completing Step 0 and 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.
Input
$ARGUMENTS = Optional focus area or question (e.g., "focus on the database layer", "what should we prioritize next"). If empty, defaults to "general next steps".
Workflow
Step 0: Compile Session Context — MANDATORY, SILENT
Before doing ANYTHING else, compile the current session state. Do NOT ask the user any questions during this step — proceed silently and autonomously.
- Read project memory: Read the project's
MEMORY.mdfrom the auto-memory directory to understand what's been worked on, recent patterns, and known issues - Recent commits: Run
git log --oneline -10to see recent work - Uncommitted work: Run
git diff --statto see what's in progress - Active tasks: Check
TaskListfor any active/pending tasks - Synthesize: Form a 1-paragraph internal "current state" summary — do NOT output this to the user, just hold it in context for Step 1
Do NOT present findings. Do NOT ask questions. Proceed directly to Step 0.5.
Step 0.5: Explore Codebase — MANDATORY, SILENT
After compiling session context (Step 0), explore the actual codebase:
- Find key files: Use
Globfor main source files (*.py, *.ts, *.js) in project root and src/ - Read recently modified: Run
git diff --name-only HEAD~5 HEAD, read up to 10 files (first 100 lines each) - Read structural files: README.md, pyproject.toml, package.json if they exist
- Synthesize: Form internal "codebase summary" — key files, purposes, connections
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 · 168 lines · 0 tokens per session scan A badc974ab5a6
export-to-council is a command published in the GitHub repository intellegix/intellegix-code-agent-toolkit (57 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,269 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
e2e
使用 Playwright 对 Web UI 进行端到端测试（支持视频录制、Trace 录制、控制台/网络日志捕获）.
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
open
SoDam-Design-Kit open 대시보드 — 검증 이력·판정서·스크린샷을 브라우저로 열람 + 재검증.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.
can-i-use
Check browser support for web platform features against the project's browser targets.
verify-pr
Verify a PR's frontend changes through browser automation.