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 agents/run-llama/llama_index/toolsgit clone --depth 1 https://github.com/run-llama/llama_indexWhat 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.01746 |
| Opus 5 | $0.00000 | $0.00873 |
| Sonnet 5 | $0.00000 | $0.00349 |
| Haiku 4.5 | $0.00000 | $0.00175 |
Grade A, and why
tools 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 yesterday.
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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Concept
Having proper tool abstractions is at the core of building agentic systems in LlamaIndex. Defining a set of Tools is similar to defining any API interface, with the exception that these Tools are meant for agent rather than human use. We allow users to define both a Tool as well as a ToolSpec containing a series of functions under the hood.
When using an agent or LLM with function calling, the tool selected (and the arguments written for that tool) rely strongly on the tool name and description of the tools purpose and arguments. Spending time tuning these parameters can result in larges changes in how the LLM calls these tools.
A Tool implements a very generic interface - simply define __call__ and also return some basic metadata (name, description, function schema).
We offer a few different types of Tools:
FunctionTool: A function tool allows users to easily convert any user-defined function into a Tool. It can also auto-infer the function schema, or let you customize various aspects.QueryEngineTool: A tool that wraps an existing query engine. Note: since our agent abstractions inherit fromBaseQueryEngine, these tools can also wrap other agents.- Community contributed
ToolSpecsthat define one or more tools around a single service (like Gmail) - Utility tools for wrapping other tools to handle returning large amounts of data from a tool
FunctionTool
A function tool is a simple wrapper around any existing function (both sync and async are supported!).
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.tools import FunctionTool
def get_weather(location: str) -> str:
"""Usfeful for getting the weather for a given location."""
...
tool = FunctionTool.from_defaults(
get_weather,
# async_fn=aget_weather, # optional!
)
agent = ReActAgent(llm=llm, tools=tools)
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.
- yesterday First seen · 200 lines · 0 tokens per session scan A 4bea6015de40
tools is an agent published in the GitHub repository run-llama/llama_index (51,923 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,746 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 agents, from other repositories
data-pipeline-engineer
Data pipeline specialist: embeddings, chunking strategies, vector indexes, data transformation for AI consumption.
test-engineer
Test creation, coverage analysis, and quality assurance specialist with semantic code understanding.
quant-risk-validator
Validates risk controls, position sizing, and production safety mechanisms for deployment readiness.
architect
System design and architectural decisions specialist with structured reasoning.
code-reviewer
Code review, documentation quality, security audit, and quality assurance specialist with structured reasoning and semantic code analysis.
reasoning-specialist
Complex analysis and structured reasoning specialist for deep problem-solving.