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/sixb-ai/sixb/running-and-streaminggit clone --depth 1 https://github.com/sixb-ai/sixbWrote 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/sixb-ai/sixb/running-and-streaming)<a href="https://agentmods.dev/agents/sixb-ai/sixb/running-and-streaming"><img src="https://agentmods.dev/badge/agents/sixb-ai/sixb/running-and-streaming.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.02102 |
| Opus 5 | $0.00000 | $0.01051 |
| Sonnet 5 | $0.00000 | $0.00420 |
| Haiku 4.5 | $0.00000 | $0.00210 |
Grade A, and why
running-and-streaming 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Running and streaming
A defined agent does nothing until a conversation drives it. You drive it over HTTP — create a thread, post a message, follow the run — and stream the run live over a websocket.
Threads, runs, and messages
- A thread is one conversation with one agent, owned by a principal. It has a status (
activeorarchived) and an ordered list of messages. - A run is one turn. Posting a user message to a thread triggers a run.
- A message has a
role(system,user,assistant) and structuredparts:text,reasoning,step-start,tool-call, andfile. The assistant message is persisted once the run finishes.
HTTP API
| Method | Path | Purpose |
|---|---|---|
GET |
/api/agents |
List agents you can run. |
GET |
/api/agents/:agentId |
Get one agent. |
GET |
/api/agent-threads |
List threads (filter by agentId, status). |
POST |
/api/agent-threads |
Create a thread ({ agentId, title?, threadId? }). |
GET |
/api/agent-threads/:threadId |
Get a thread. |
GET |
/api/agent-threads/:threadId/messages |
List a thread's messages. |
POST |
/api/agent-threads/:threadId/messages |
Post a user message — triggers a run. |
GET |
/api/agent-threads/:threadId/runs |
List a thread's runs. |
POST |
/api/agent-threads/:threadId/runs/:runId/retry |
Retry a failed run without adding another user message. |
POST |
/api/agent-threads/:threadId/cancel |
Cancel the thread's queued or running run ({ runId }). |
GET |
/api/agent-runs/:runId |
Get a run's status. |
GET |
/api/agent-threads/:threadId/messages/:messageId/files/content |
Download a file attached to a message. |
Trigger a run
There is no separate run-trigger endpoint — posting a message is the trigger. The 202 response
returns the canonical durable run:
// POST /api/agent-threads/:threadId/messages { "text": "Which invoices are overdue?" }
{
"run": {
"id": "run_...",
"threadId": "thr_...",
"agentId": "accounts",
"triggerMessageId": "msg_...",
"requestedBy": { "type": "user", "id": "usr_..." },
"status": "queued",
"attempt": 0,
"streamId": "agents.runs.run_...",
"createdAt": "2026-07-11T20:00:00.000Z"
}
}
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 Changed · +6 lines 893f6aa3f6f8
- 5d ago First seen · 168 lines · 0 tokens per session scan A 8b563e43466c
running-and-streaming is an agent published in the GitHub repository sixb-ai/sixb (61 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,102 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
VoltAgent's Memory class stores conversation history and enables agents to maintain context across interactions. Supports persistent storage, semantic search, and working memory.
streaming
Streaming is key to building responsive applications. There are a few types of data you’ll want to stream.
web-research-analyst
Web research: browser automation, Tavily API, competitive intelligence, documentation capture, technical recon.
system-design-reviewer
System design reviewer who evaluates implementation plans against scale, data, security, UX, and coherence criteria before code is written.
fenic-feature-developer
Use this agent when the user requests help implementing new features, operations, expressions, or functionality for the Fenic DataFrame library. This includes:\n\n- Adding new DataFrame operations (e.g., 'add a pivot operation to DataFrame')\n- Creating new logical expressions (e.g., 'implement a regexextract…
Analytics Engineer
Models semantic layers, defines business metrics, designs data marts, and encodes business logic in SQL. Invoke with $ae.