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/02-agent-modesgit 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/02-agent-modes)<a href="https://agentmods.dev/agents/smythos/sre/02-agent-modes"><img src="https://agentmods.dev/badge/agents/smythos/sre/02-agent-modes.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 | $0.00000 | $0.01034 |
| Opus 5 | $0.00000 | $0.00517 |
| Sonnet 5 | $0.00000 | $0.00207 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
02-agent-modes 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 4d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Modes
Agent modes are pluggable execution strategies that augment how an agent processes and responds to tasks. Each mode adds specialized capabilities through additional behavior (system prompt) instructions and hidden skills, all managed transparently by the SDK.
Available Modes
| Mode | Enum Value | Description |
|---|---|---|
| Default | TAgentMode.DEFAULT |
No extra capabilities. The agent uses only the skills and behavior you provide. |
| Planner | TAgentMode.PLANNER |
Adds systematic planning, task tracking, and progress reporting. |
| Worker | TAgentMode.WORKER |
Adds background task delegation to "copy" agents while the main agent stays interactive. |
Setting a Mode
Single Mode
import { Agent, TAgentMode } from '@smythos/sdk';
const agent = new Agent({
name: 'Research Assistant',
model: 'gpt-4o',
behavior: 'You are a helpful research assistant.',
mode: TAgentMode.PLANNER,
});
Combining Multiple Modes
Modes can be combined using an array. Each mode's capabilities are layered on top of each other:
const agent = new Agent({
name: 'Research Assistant',
model: 'gpt-4o',
behavior: 'You are a helpful research assistant.',
mode: [TAgentMode.PLANNER, TAgentMode.WORKER],
});
When combining Planner and Worker modes, the agent will plan complex tasks into steps (Planner) and dispatch heavy subtasks to background workers (Worker).
How Modes Work Under the Hood
When a mode is applied to an agent, two things happen:
- Behavior (system prompt) extension: The mode appends instructions to the agent's
behavior, telling the LLM how to use the mode's capabilities. - Hidden skills: The mode registers internal skills (prefixed with
_sre_) that the LLM can call. These skills are not visible to end users but power the mode's functionality.
All mode-managed skills are automatically filtered out when creating copy agents (Worker mode) or exporting agent configurations.
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.
- 4d ago First seen · 139 lines · 0 tokens per session scan A 18fc2095512f
02-agent-modes 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,034 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
memory
LangGraph supports two types of memory essential for building conversational agents.
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.
streaming
Streaming is key to building responsive applications. There are a few types of data you’ll want to stream.
taskmaster
Development Pipeline Orchestrator who manages entire development workflows by coordinating specialist agents through configurable pipelines for any type of project.
codecrusher
Senior Developer & Implementation Expert who transforms architectural plans into high-quality, production-ready code across any technology stack.
ship-and-babysit
Commit local changes, push the branch to the user's fork, open or reuse a PR against tinyhumansai/openhuman:main, then babysit CI and CodeRabbit feedback until the PR is green and clean. Use when the user wants an end-to-end ship flow, not just implementation.