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 skills add stevengonsalvez/agents-in-a-box --skill daemonsgit clone --depth 1 https://github.com/stevengonsalvez/agents-in-a-boxWrote 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/daemons)<a href="https://agentmods.dev/skills/stevengonsalvez/agents-in-a-box/daemons"><img src="https://agentmods.dev/badge/skills/stevengonsalvez/agents-in-a-box/daemons/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/daemons"><img src="https://agentmods.dev/badge/skills/stevengonsalvez/agents-in-a-box/daemons.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.00126 | $0.02205 |
| Opus 5 | $0.00063 | $0.01103 |
| Sonnet 5 | $0.00025 | $0.00441 |
| Haiku 4.5 | $0.00013 | $0.00220 |
Grade A, and why
ainb-fleet:daemons 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 8d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ainb fleet:daemons — daemon health view
The runtime-health answer for the fleet's four background daemons. Reads the
on-disk liveness signals each daemon already maintains and renders one typed
row per daemon. The same aggregator (fleet::daemons::collect) backs the TUI
Daemons screen, so the CLI and the TUI can never drift.
This is the question ainb fleet bridge status could never answer: that verb
reports only install state. daemons reports whether the process is
actually running and serving right now — a crashed-but-installed bridge
shows stopped with a stale-heartbeat reason here.
The four daemons
| daemon | id | how it's probed |
|---|---|---|
| phone bridge | bridge |
heartbeat file (~/.agents-in-a-box/daemons/bridge.json) + pid-identity cross-check |
| notifyd | notifyd |
PID-file liveness + bound Unix socket + sqlite DB file present |
| ATC | atc |
mode-dependent: in full, the most-recently-beating instance's heartbeat-state.json (timer-driven; no resident pid); in lite, the scan loop's own heartbeat + pid |
| fleet daemon | fleet-daemon |
heartbeat file + pid-identity cross-check — conditional row, see below |
Rows are emitted in this exact order (bridge, notifyd, ATC, then the fleet daemon when it has a row), even when every daemon is stopped — so "everything stopped" is a legible table, never an empty one.
The fleet daemon is a conditional row. ATC is the fleet's supervisor and the standalone daemon is what it replaced, so a permanently-stopped row for it presented the two as a choice — the competing control path the supervisor exists to remove, still on the screen you read to see who is running. It is therefore listed only when it is NOT stopped.
That is deliberately not "always hidden". A daemon that is up got there through
--force-race, which means two controllers really are auto-continuing the same
panes and ATC's per-session retry cap cannot hold. That row appears, reports
degraded, and its reason opens with RACING ATC. Hiding it would make the one
state you most need to see the only one the screen does not show.
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.
- 8d ago Changed · +24 lines 18e023029091
- 12d ago First seen · 140 lines · 126 tokens per session scan A 1b5b4c7eb983
ainb-fleet:daemons is a skill published in the GitHub repository stevengonsalvez/agents-in-a-box (23 stars, last pushed today), licensed MIT. It adds 126 tokens to every session and 2,205 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.