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 skills add RasaHQ/rasa-agent-skills --skill rasa-setting-up-react-agentsgit clone --depth 1 https://github.com/RasaHQ/rasa-agent-skillsWrote 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/skills/rasahq/rasa-agent-skills/rasa-setting-up-react-agents)<a href="https://agentmods.dev/skills/rasahq/rasa-agent-skills/rasa-setting-up-react-agents"><img src="https://agentmods.dev/badge/skills/rasahq/rasa-agent-skills/rasa-setting-up-react-agents/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/skills/rasahq/rasa-agent-skills/rasa-setting-up-react-agents"><img src="https://agentmods.dev/badge/skills/rasahq/rasa-agent-skills/rasa-setting-up-react-agents.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.00061 | $0.02874 |
| Opus 5 | $0.00030 | $0.01437 |
| Sonnet 5 | $0.00012 | $0.00575 |
| Haiku 4.5 | $0.00006 | $0.00287 |
Grade A, and why
rasa-setting-up-react-agents 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 9d 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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuring ReAct Sub Agents
ReAct sub agents are built-in autonomous agents that dynamically choose which MCP tools to invoke based on conversation context. They operate in a ReAct (Reasoning + Acting) loop — the agent reasons about the user's request, picks a tool, observes the result, and repeats until the task is done.
MCP servers must be defined in endpoints.yml before configuring a ReAct sub agent.
See the rasa-configuring-mcp-server skill for server setup and authentication.
This feature is in beta and available starting from Rasa 3.14.0.
Workflow
- Ensure the MCP server is defined in
endpoints.yml(seerasa-configuring-mcp-serverskill). - Create the sub agent directory with a
config.yml(see "Directory structure" and "Configuration"). - Choose between general-purpose or task-specific agent type (see "General-purpose vs task-specific").
- Optionally filter which MCP tools the agent can access (see "Tool filtering").
- Invoke the sub agent from a flow using a
callstep (see "Invoking from a flow"). - Optionally customize the prompt, input/output processing, or add custom tools (see "Customization").
- Validate the project.
Directory structure
Each ReAct sub agent lives in its own subdirectory under sub_agents/. Both
rasa train and rasa run scan this directory by default; pass --sub-agents <path>
to either command to use a different directory.
The agent name must be unique across all sub agents and all flow IDs.
your_project/
├── config.yml
├── endpoints.yml
├── domain/
├── data/flows/
└── sub_agents/
└── stock_explorer/
├── config.yml # required
├── prompt_template.jinja2 # optional
└── custom_agent.py # optional
Configuration
The sub agent's config.yml connects the agent to one or more MCP servers defined in
endpoints.yml. The protocol defaults to RASA — do not set it to A2A.
# sub_agents/stock_explorer/config.yml
agent:
name: stock_explorer
description: "Agent that helps users research and analyze stock options"
configuration:
llm: # optional, default model is provided by Rasa codebase
model_group: my_llm
prompt_template: sub_agents/stock_explorer/prompt_template.jinja2 # optional
timeout: 30 # optional, seconds before timing out
max_retries: 3 # optional, MCP connection retries
include_date_time: true # optional, default: true
timezone: "America/New_York" # optional, default: "UTC"
connections:
mcp_servers:
- name: trade_server
include_tools:
- find_symbol
- get_company_news
- fetch_live_price
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.
- 9d ago First seen · 319 lines · 61 tokens per session scan A 63f481bb649a
rasa-setting-up-react-agents is a skill published in the GitHub repository RasaHQ/rasa-agent-skills (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 2,874 once invoked, about $0.0003 per session on Opus 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…