overview

Documentation for defining an agent: a conversational assistant configured with instructions, a language model, selected tools, and access to project data through Sixb. Agents are declared in an agents/ directory and can be used through HTTP or a websocket.

In plain words
What is it for?
Use it to define agents such as a business analyst, choose their model and instructions, select tools and groups, and expose them to client applications.
Why use it?
It explains the parts of an agent and how they fit together, so you can create one without guessing the project structure or configuration.

Agent

Install

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.

agentmods
npx agentmods add agents/sixb-ai/sixb/overview
Clone the repo
git clone --depth 1 https://github.com/sixb-ai/sixb
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 740 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00740
Opus 5 $0.00000 $0.00370
Sonnet 5 $0.00000 $0.00148
Haiku 4.5 $0.00000 $0.00074

Measured 2d ago against content hash 028ee10f5082, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

overview 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 2d 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.

docs/agents/overview.md · 74 lines

How it starts

The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agents

An agent is a conversational assistant you define alongside your ontology. It calls a language model, selected worker tools, sandboxed read and bash, and an authorized Sixb API.

You define an agent declaratively and export it from agents/; createSixb() discovers it. A worker runs it, and clients drive it over HTTP and a websocket.

Define an agent

Put each definition in agents/ and export it.

// agents/business-analyst.ts
import { defineAgent } from "@sixb/core"
import { gateway } from "ai"

export const businessAnalyst = defineAgent("business-analyst", {
  name: "Business Analyst",
  description: "Investigates customers, invoices, projects, and follow-ups.",
  model: gateway("deepseek/deepseek-v4-flash"),
  instructions: [
    "You are the business operations analyst for this project.",
    "Ground answers in the data available through Sixb, and say when data is insufficient.",
    "Prefer concise summaries with clear next actions.",
  ].join("\n"),
})

See Defining agents for every config field.

Core concepts

Concept What it is
Definition The agent you write with defineAgent — model, instructions, groups, selected tools, and loop limits.
Thread One conversation with an agent, owned by a principal.
Run One turn. Posting a user message triggers a run.
Message A system, user, or assistant message made of text, reasoning, step-start, and tool-call parts.
Tools Explicitly selected worker tools plus built-in read and bash in a sandbox.

Run an agent

Defining an agent needs nothing extra. Running one needs two things:

  • The agent-worker process. bun sixb dev runs it for you; in production run it like the other workers.
  • A sandbox factorycreateSixb({ sandboxes }). The worker won't start without one, because the read and bash tools run in a sandbox.
import { createSixb } from "@sixb/core"
import { SmolvmSandboxFactory } from "@sixb/sandboxes-smolvm"

export const sixb = createSixb({
  id: "acme-corp",
  // ...storage, broker, queues
  sandboxes: new SmolvmSandboxFactory(),
})

Read the full file on GitHub · 74 lines

Changes

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.

  1. 2d ago First seen · 74 lines · 0 tokens per session scan A 028ee10f5082

Subscribe to this mod's changes

overview is an agent published in the GitHub repository sixb-ai/sixb (53 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 740 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.