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/creative-researchgit 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.02907 |
| Opus 5 | $0.00000 | $0.01453 |
| Sonnet 5 | $0.00000 | $0.00581 |
| Haiku 4.5 | $0.00000 | $0.00291 |
Grade A, and why
creative-research 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 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.
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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/creative-research — 3-Stage Creative Feature Discovery
Run a divergent ideation pipeline to discover novel features for the current project. Unlike convergent research commands (/research-perplexity, /export-to-council), this command brainstorms new ideas the user hasn't thought of, then scores viability and generates implementation blueprints.
3 sequential Perplexity queries via Playwright — ~5-7 min total, $0/query.
CRITICAL: Do NOT ask the user questions before completing Step 0 and Stage 1. Compile context silently, build all queries, and execute. Only interact after Stage 3 results are ready.
Input
$ARGUMENTS = Optional focus area for creativity (e.g., "AI-powered features", "developer experience", "monetization"). If empty, brainstorm broadly across all dimensions.
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
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, CLAUDE.md if they exist
- Synthesize: Form internal "codebase summary" — key files, purposes, architecture, tech stack
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 · 253 lines · 0 tokens per session scan A 1894e63b2a58
creative-research 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 2,907 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.
agentlas-cloud
Staff a task only from the signed-in owner's Agent Cloud agents.
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.
tldr
Re-apply TLDR rules for this turn (verdict first, no filler).
me-figure-discussion
Write or review thermal-fluid figure discussion with observation, physical mechanism, comparison, uncertainty, and claim limits.
execute
Interactive workflow for workspace isolation, pane-delegated implementation, testing, review, and cleanup.