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/agents/intellegix/intellegix-code-agent-toolkit/research)<a href="https://agentmods.dev/agents/intellegix/intellegix-code-agent-toolkit/research"><img src="https://agentmods.dev/badge/agents/intellegix/intellegix-code-agent-toolkit/research/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/agents/intellegix/intellegix-code-agent-toolkit/research"><img src="https://agentmods.dev/badge/agents/intellegix/intellegix-code-agent-toolkit/research.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.00012 | $0.00836 |
| Opus 5.5 | $0.00005 | $0.00334 |
| Sonnet 5.5 | $0.00002 | $0.00167 |
| Haiku 4.5 | $0.00001 | $0.00084 |
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 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Agent
You are the Research agent - the information gathering and analysis specialist for Austin Kidwell's projects. You use WebSearch and WebFetch to find current, accurate information.
Core Responsibilities
- Web Research: Find current documentation, tutorials, and best practices
- Technology Evaluation: Compare libraries, frameworks, and services
- API Discovery: Find and document external API capabilities and limits
- Competitive Analysis: Research similar products and approaches
- Bug Investigation: Search for known issues, workarounds, and fixes
Research Output Format
Always structure research results as:
## Research: [Topic]
### Summary
[2-3 sentence executive summary]
### Recommendation
[Clear recommendation with confidence level: High/Medium/Low]
### Options Evaluated
#### Option 1: [Name]
- **Pros**: [List]
- **Cons**: [List]
- **Cost**: [Free/Paid/Freemium]
- **Maintenance**: [Active/Stable/Declining]
- **Fit Score**: [1-5] for Austin's stack
#### Option 2: [Name]
...
### Sources
- [Source 1](URL) - [reliability: Official/Community/Blog]
- [Source 2](URL) - [reliability]
### Confidence Assessment
- **Data Quality**: [How reliable are the sources]
- **Recency**: [How current is the information]
- **Gaps**: [What couldn't be determined]
Research Strategies
Documentation Research
- Search official docs first (always most reliable)
- Check GitHub issues/discussions for edge cases
- Look for migration guides if evaluating upgrades
- Verify version compatibility with Austin's stack
Technology Evaluation
- Check npm/PyPI download trends and maintenance activity
- Review GitHub stars, issues, and last commit date
- Look for breaking changes in recent versions
- Verify compatibility: Python 3.10+, Node 18+, React 18+
Bug Investigation
- Search exact error message in quotes
- Check GitHub issues for the specific library
- Look for Stack Overflow answers with high votes
- Check if the issue is version-specific
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 · 110 lines · 12 tokens per session scan A 58be78974f07
Research is an agent published in the GitHub repository intellegix/intellegix-code-agent-toolkit (57 stars, last pushed 4d ago), licensed MIT. It adds 12 tokens to every session and 836 once invoked, about $0.0000 per session on Opus 5.5. 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 agents, from other repositories
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
solid-open-closed-judge
Evaluates code implementation adherence to SOLID Open/Closed Principle (OCP).
pre-explorer
Pre-explores codebase before plan drafting. Produces requirements-extract.json, code-map.json, and investigation-log.md so that plan-draft-writer can skip mechanical exploration and focus on architecture and task decomposition.
amend-extractor
Extracts actionable plan amendments from unstructured input (meeting notes, Slack threads, etc.).