Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/stevengonsalvez/agents-in-a-boxnpx agentmods add skills/stevengonsalvez/agents-in-a-box/standupWrote 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/skills/stevengonsalvez/agents-in-a-box/standup)<a href="https://agentmods.dev/skills/stevengonsalvez/agents-in-a-box/standup"><img src="https://agentmods.dev/badge/skills/stevengonsalvez/agents-in-a-box/standup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/stevengonsalvez/agents-in-a-box/standup"><img src="https://agentmods.dev/badge/skills/stevengonsalvez/agents-in-a-box/standup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00113 | $0.01404 |
| Opus 5 | $0.00056 | $0.00702 |
| Sonnet 5 | $0.00023 | $0.00281 |
| Haiku 4.5 | $0.00011 | $0.00140 |
Grade A, and why
ainb-fleet:standup 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 11d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ainb fleet:standup
List every claude session across the host. Three sources merged + deduped by cwd.
What standup reads vs what needs reads
standup is a roster: it merges discovery sources (ainb + claude-peers
broker + background jobs) and attaches a JSONL-synthesised summary line per
session. It does not read the event-sourced current_state table itself —
it is a "who is running" snapshot, not a "who is blocked" classifier.
The block-detection lives in /ainb-fleet:needs, which is
hooks-primary: it reads the materialized current_state table (ASK / ERR /
WAIT / IDLE / RUNNING / DONE), sourced from Claude Code hooks via
events.jsonl → notifyd, with a tmux/transcript fallback for non-Claude agents
(Codex/Gemini fire no Claude hooks). Standup's job is to spot when a session
looks answerable (summary contains AskUserQuestion) and auto-chain to
needs for the authoritative read + routing (see below).
Neither skill installs hooks — they consume materialized state. The global Claude Code hooks are installed by
ainb fleet atc setup.
Run
ainb fleet standup # text table (default)
ainb --format json fleet standup # JSON for piping
ainb fleet standup --no-enrich # 0-token roster (env AINB_FLEET_ENRICH=0)
--format is a global flag — it may appear anywhere (ainb --format json fleet standup or ainb fleet --format json standup both work); the
global-first form above is the convention across the fleet skills.
The workflow-backed briefing (/ainb-fleet:jarvis verb=standup) drafts the
per-session "what it's doing" lines in a single batched agent, not one per
session. --no-enrich skips that entirely.
Output fields (JSON)
| field | meaning |
|---|---|
id |
session id (peer id preferred, else ainb session_id, else bg job id) |
cwd |
working dir — primary dedupe key |
pid |
OS pid (when known — peers + bg jobs publish; ainb does not) |
tmux_session |
tmux session name if running in tmux |
workspace_name |
ainb workspace name |
worktree_path |
ainb worktree path |
peer_id |
broker peer id (if registered) |
sources |
array — subset of ["ainb","peers","jobs"] |
summary |
peer-published summary (may start with WAITING: to flag block) |
last_seen_ms |
unix ms of last activity any source observed |
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.
- 11d ago First seen · 145 lines · 113 tokens per session scan A 34648d4b01cb
ainb-fleet:standup is a skill published in the GitHub repository stevengonsalvez/agents-in-a-box (23 stars, last pushed today), licensed MIT. It adds 113 tokens to every session and 1,404 once invoked, about $0.0006 per session on Opus 5. 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 skills, from other repositories
chinese-git-workflow
A Git workflow guide tailored to Chinese-hosted platforms such as Gitee, Coding.net, and GitLab, including their code-review and build systems.
chinese-commit-conventions
A Chinese-language convention for writing Git commit messages, based on Conventional Commits, a standard format that tools can use to classify changes and build changelogs.
using-superpowers
A set of rules for finding and using assistant skills at the start of every conversation. It says to check for relevant skills before responding, including when asking a clarification question.
chinese-code-review
Chinese-language guidance for giving professional, tactful code-review feedback while still calling out real problems.
mcp-builder
A guide to building MCP servers, which let AI assistants call tools or read connected data. It covers server structure, tool design, validation, testing and deployment in TypeScript and Python.
platform-api
Queries the Genesys Cloud Platform API schema for endpoint details, permissions, parameters, and response formats. Use when user asks about Genesys Cloud API endpoints (e.g., "/api/v2/assistants/queues"), API documentation, API permissions, schemas, capabilities, or when implementing Genesys Cloud operations.