SmythOS Runtime Environment is an open-source runtime and software development kit for building and running AI agents. Developers use it to create, orchestrate, and manage agents across local, cloud, and edge environments, with abstractions for language models, vector databases, storage, and caching. The catalogue add-ons support work with this runtime.
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/smythos/sre/03-planner-modegit clone --depth 1 https://github.com/SmythOS/sreWrote 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/smythos/sre/03-planner-mode)<a href="https://agentmods.dev/agents/smythos/sre/03-planner-mode"><img src="https://agentmods.dev/badge/agents/smythos/sre/03-planner-mode.svg" alt="Measured on agentmods" 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.00000 | $0.01560 |
| Opus 5 | $0.00000 | $0.00780 |
| Sonnet 5 | $0.00000 | $0.00312 |
| Haiku 4.5 | $0.00000 | $0.00156 |
Grade A, and why
03-planner-mode 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 6d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planner Mode
Planner mode gives an agent systematic planning capabilities. When the agent receives a complex or multi-step task, it will create a structured plan, track each step's progress, and verify completion before finishing.
This mode is ideal for tasks that require methodical execution: code generation with multiple files, research with several phases, or any workflow where step-by-step transparency matters.
See the Planner Mode Example for a complete, runnable implementation.
Enabling Planner Mode
import { Agent, TAgentMode } from '@smythos/sdk';
const agent = new Agent({
name: 'Code Assistant',
behavior: 'You are a senior developer who writes clean, well-tested code.',
model: 'gpt-4o',
mode: TAgentMode.PLANNER,
});
How It Works
When a user sends a complex request, the agent will:
- Analyze the request and reason about the approach (in
<thinking>tags) - Plan the steps needed (in
<planning>tags) - Register the plan as tracked tasks via the internal
_sre_Plan_Tasksskill - Execute each step sequentially, updating task status along the way
- Verify that all tasks are completed before finishing
The agent communicates its reasoning transparently using <thinking> tags, and uses <planning> tags to outline its approach. These tags allow the LLM to separate internal reasoning from user-facing output.
Events
Planner mode emits events on the agent object so you can build UIs that reflect the agent's progress in real time.
TasksAdded
Fired when the agent creates a new plan.
agent.on('TasksAdded', (tasksList, allTasks) => {
// tasksList: the newly added tasks
// allTasks: all tasks in the planner (cumulative)
for (const [id, task] of Object.entries(allTasks)) {
console.log(`${task.status}: ${task.summary || task.description}`);
}
});
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.
- 6d ago First seen · 202 lines · 0 tokens per session scan A c991f168a758
03-planner-mode is an agent published in the GitHub repository SmythOS/sre (1,289 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,560 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
multi-agent
A single agent might struggle if it needs to specialize in multiple domains or manage many tools. To tackle this, you can break your agent into smaller, independent agents and composing them into a multi-agent system.
context
Agents often require more than a list of messages to function effectively. They need context.
memory
LangGraph supports two types of memory essential for building conversational agents.
tools
Tools are a way to encapsulate a function and its input schema in a way that can be passed to a chat model that supports tool calling. This allows the model to request the execution of this function with specific inputs.
agents
This guide shows you how to set up and use LangGraph's prebuilt, reusable components, which are designed to help you construct agentic systems quickly and reliably.
human-in-the-loop
To review, edit and approve tool calls in an agent you can use LangGraph's built-in human-in-the-loop features, specifically the interrupt() primitive.