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/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.00442 |
| Opus 5 | $0.00000 | $0.00221 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Research
Conduct comprehensive research on: $ARGUMENTS
Research Process
Phase 1: Initial Search
-
Understand the query
- Break down the research question into key concepts
- Identify what type of information is needed (technical, business, implementation, etc.)
-
Search for authoritative sources
- Use WebSearch to find recent, relevant information
- Prioritize official documentation, academic papers, and trusted technical blogs
- Look for multiple perspectives on the topic
Phase 2: Deep Dive
-
Fetch and analyze key sources
- Use WebFetch to read full content from promising URLs
- Extract relevant code examples, patterns, and best practices
- Note any caveats, limitations, or version-specific information
-
Cross-reference findings
- Compare information across sources
- Identify consensus vs. disputed approaches
- Note any outdated information (check dates)
Phase 3: Synthesize
- Compile findings
- Organize information by relevance to the original query
- Highlight practical takeaways
- Include code examples where applicable
Output Format
# Research: [Topic]
## Summary
[2-3 sentence executive summary]
## Key Findings
### Finding 1: [Topic]
[Details with source attribution]
### Finding 2: [Topic]
[Details with source attribution]
## Practical Recommendations
1. [Actionable recommendation]
2. [Actionable recommendation]
## Code Examples (if applicable)
```[language]
// Example implementation
Sources
Caveats & Limitations
- [Any important warnings or version-specific notes]
Related Topics for Further Research
- [Topic 1]
- [Topic 2]
## Research Quality Standards
- Cite all sources with URLs
- Distinguish between facts and opinions
- Note information freshness (publication dates)
- Flag any conflicting information found
- Prefer primary sources over secondary
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 · 77 lines · 0 tokens per session scan A 525cf859b5e7
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 442 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).
execute
Interactive workflow for workspace isolation, pane-delegated implementation, testing, review, and cleanup.
me-figure-discussion
Write or review thermal-fluid figure discussion with observation, physical mechanism, comparison, uncertainty, and claim limits.