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 atcgit 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/atc)<a href="https://agentmods.dev/skills/stevengonsalvez/agents-in-a-box/atc"><img src="https://agentmods.dev/badge/skills/stevengonsalvez/agents-in-a-box/atc/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/atc"><img src="https://agentmods.dev/badge/skills/stevengonsalvez/agents-in-a-box/atc.svg" alt="Reviewed on agentmods" width="80" 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.00254 | $0.03688 |
| Opus 5 | $0.00127 | $0.01844 |
| Sonnet 5 | $0.00051 | $0.00738 |
| Haiku 4.5 | $0.00025 | $0.00369 |
Grade B, and why
ainb-fleet:atc scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Code hooks into ~/.claude/settings.json. It auto-clears the safe/blocked How it starts
The opening of the file, as written. The whole thing — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ainb fleet:atc — Air Traffic Control
ATC is the orchestrating brain that ties the fleet verbs together on a schedule
with a policy. It is a real ainb run Claude session reading a generated
CLAUDE.md, woken every N minutes by an OS timer. On each heartbeat it pulls
the LLM-free ainb fleet needs --format json read, auto-clears the safe
cases itself, and pages you (via the phone bridge) only for the calls that
genuinely need a human.
hooks ─▶ events.jsonl ─▶ notifyd ─▶ current_state (ASK/ERR/WAIT/IDLE/RUNNING/DONE)
│ (materialized per session)
OS timer ──[HEARTBEAT]──▶ ATC session ──reads──▶ ainb fleet needs --format json
│ (hooks-primary, tmux fallback)
├─ auto-clear ─▶ ainb fleet broadcast (answer / continue)
└─ escalate ───▶ phone bridge ─▶ your phone
How ATC learns a session is blocked — HOOKS-PRIMARY
The fleet needs read ATC runs each heartbeat is event-sourced, not pane-
scraped. Claude Code hooks append lifecycle events to events.jsonl; notifyd
ingests them into a SQLite current_state table that materializes the latest
stage per session (ASK / ERR / WAIT / IDLE / RUNNING / DONE). ATC reads that
materialized state as the PRIMARY source — so it learns ASK/WAIT/IDLE/ERR from
hooks, the instant they fire, without scraping panes. The tmux pane scan is
only the fallback for sessions the hooks don't cover: non-Claude agents
(Codex/Gemini fire no Claude hooks) and any session not yet materialized.
ainb fleet atc setup is what installs those global hooks into
~/.claude/settings.json (the --no-hooks flag skips it). The consumer skills
(needs, fleet-needs, standup) do NOT install hooks — they only read the
materialized state. So provisioning ATC is also what turns the whole fleet
hooks-primary; without it (or without atc setup's hook install), fleet needs
falls back to the live pane scan everywhere and still works.
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 · +73 lines · +49 tokens per session 1c4df64656d1
- 11d ago First seen · 239 lines · 205 tokens per session scan B 9e2edd39ab5a
ainb-fleet:atc is a skill published in the GitHub repository stevengonsalvez/agents-in-a-box (23 stars, last pushed today), licensed MIT. It adds 254 tokens to every session and 3,688 once invoked, about $0.0013 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.