Help us improve
Share bugs, ideas, or general feedback.
From agentops
Generates an orientation report for fresh agent sessions in AgentOps repositories. Confirms key configuration files, counts ready beads, and probes agent mail. Automatically invoked for every spawned agent.
npx claudepluginhub boshu2/agentops --plugin agentopsHow this skill is triggered — by the user, by Claude, or both
Slash command
/agentops:session-bootstrapThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **One-line value:** every agent in the swarm starts with the same orientation report, regardless of model.
Initializes AgentOps project files (GOALS.md, PRODUCT.md, .agents/) using the ao CLI. Useful for setting up or completing a project scaffold.
Runs a checklist for onboarding new agents to the bOpen team: design, write, avatar, plugin, Paperclip registration, roster, and optional ClawNet bot deployment.
Manages agent fleets via CRUD (create, command, monitor, delete) and lifecycle patterns. For multi-agent systems, resource cleanup, and state tracking with Claude Agent SDK.
Share bugs, ideas, or general feedback.
ao session bootstrap — the universal init promptOne-line value: every agent in the swarm starts with the same orientation report, regardless of model.
Every agent spawned into an AgentOps repository runs this first. No exceptions. The bootstrap is the contract that makes the future fungibility charter (soc-vuu6.29) operational: identical starting frames let you swap Claude for Codex (or vice versa) on any bead without re-orienting.
Triggers:
ao session bootstrap.hooks-authoring skill, it can fail-open auto-fire ao session bootstrap --robot and discard the exit code.ao session bootstrap --json before claiming work.If you spawned without running it: stop, run it, then resume.
Four fail-open substeps, each producing a field in the session-bootstrap.v1 schema:
AGENTS.md and the post-soc-vuu6.3 siblings (AGENTS-WORKFLOW.md, AGENTS-CI.md, AGENTS-CODEX.md, AGENTS-RUNTIME.md). Reports which exist. The agent reads them itself once oriented; the bootstrap just confirms presence.onboard --auto — the future task-routed reading list subcommand under soc-vuu6.9. Currently P3 / not yet implemented: bootstrap falls back to phase="skipped:not-implemented" and continues without blocking.bd ready --json length. Surfaces what's immediately claimable. Fails to null if bd is missing or errors.null. Skipped with --no-mail or env MCP_AGENT_MAIL_DISABLED=1.| Flag | Effect |
|---|---|
--json | Emit the full status object (machine-readable, matches the v1 schema) |
--robot | Same as --json plus a tight exit-code contract for opt-in SessionStart hooks |
--no-mail | Skip the mcp-agent-mail probe even when the MCP server is reachable |
Default (no flags): one-line human summary on stdout, plus a stderr warning if AGENTS.md is missing.
{
"agents_md_read": true,
"agents_siblings_read": ["AGENTS-WORKFLOW.md", "AGENTS-CI.md", "AGENTS-CODEX.md", "AGENTS-RUNTIME.md"],
"onboard_phase": "skipped:not-implemented",
"ready_beads_count": 12,
"mail_unread_count": null,
"runtime": "claude-code",
"started_at": "2026-05-21T01:50:00Z",
"bootstrap_version": "v1"
}
Schema at schemas/session-bootstrap.v1.schema.json — every field is required; nullable fields carry null when the substep was skipped or errored.
The agent-fungibility-philosophy mandates: one init prompt for every agent regardless of type. Today every operator hand-rolls orientation: "read AGENTS.md, check bd ready, register with the mail server, then start." Two agents spawned by two different operators don't have the same starting frame. That's anti-fungibility — the swarm can't safely swap them mid-bead.
ao session bootstrap is the operational primitive that closes the gap. It's deliberately tiny: ~50 LOC Go + a JSON schema. It does the same four things every time, in the same order, with the same fail-open semantics. Then the agent reads the orientation tier-split itself.
AGENTS.md themselves.bd binary, an unavailable MCP server, or a deferred onboard produces a null/skipped marker and the command still exits 0. The agent decides what to do with degraded orientation.onboard --auto subcommand) — when implemented, bootstrap's onboard substep wires through automatically via subprocess shellout.cli/cmd/ao/session_bootstrap_test.go — 8 cases (full status, missing AGENTS.md, partial split, no-mail flag, runtime detection, human summary, JSON round-trip).validate-skill-frontmatter keeps the SKILL.md frontmatter contract intact.validate-session-bootstrap-schema if schema-drift becomes a concern.AGENTS.md — orientation entry-point that points here.AGENTS-WORKFLOW.md — what to do after bootstrap reports.schemas/session-bootstrap.v1.schema.json — full output contract.