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 inclusionAI/Avernet --skill bcs-http-skillsgit clone --depth 1 https://github.com/inclusionAI/AvernetWrote 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/inclusionai/avernet/bcs-http-skills)<a href="https://agentmods.dev/skills/inclusionai/avernet/bcs-http-skills"><img src="https://agentmods.dev/badge/skills/inclusionai/avernet/bcs-http-skills/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/inclusionai/avernet/bcs-http-skills"><img src="https://agentmods.dev/badge/skills/inclusionai/avernet/bcs-http-skills.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.00039 | $0.00655 |
| Opus 5 | $0.00019 | $0.00328 |
| Sonnet 5 | $0.00008 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
bcs-coordination 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 10d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BCS Multi-Bot Coordination
Use this skill when a task needs multiple bots to collaborate, exchange context, create a group, ask another bot for help, or route messages through BCS.
Requirements
bcs-cliis available onPATH.BOT_DATA_DIRpoints to the bot data directory.BCS_API_BASE_URLpoints to the BCS HTTP API, for examplehttp://127.0.0.1:21000.- A bot token is available through
BCN_BOT_TOKENor$BOT_DATA_DIR/.bcs/session.json.
Session File
$BOT_DATA_DIR/.bcs/session.json may contain:
{
"bot_uuid": "bot-demo",
"token": "replace-with-bot-token",
"api_base_url": "http://127.0.0.1:21000"
}
Command Pattern
BOT_DATA_DIR="$BOT_DATA_DIR" bcs-cli --url "$BCS_API_BASE_URL" <subcommand> [options]
Do not hard-code deployment URLs or credentials in prompts, scripts, or skill files. Use environment variables or the session file instead.
Common Commands
# Discover bots
bcs-cli --url "$BCS_API_BASE_URL" discover --query "database"
bcs-cli --url "$BCS_API_BASE_URL" discover --query "deployment" \
--skill "code_review" --skill "sql"
# Ask for group help
bcs-cli --url "$BCS_API_BASE_URL" request-group-help --topic "Investigate a production issue"
# Create a group directly when participants are known
bcs-cli --url "$BCS_API_BASE_URL" create-group \
--driver "bot-coordinator" \
--participants "bot-dba,bot-security" \
--topic "Incident analysis"
# Create a manager-worker group; all participants are assigned the worker role
bcs-cli --url "$BCS_API_BASE_URL" create-group \
--manager "bot-manager" \
--participants "bot-worker-1,bot-worker-2" \
--topic "Parallel implementation"
# Send a direct message to a bot
bcs-cli --url "$BCS_API_BASE_URL" chat \
--bot-uuid "bot-dba" \
--message "Please inspect the migration plan."
discover --skill is repeatable. Each value is an exact, case-insensitive
skill match; all skills and --query are combined with AND semantics.
References
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.
- 10d ago First seen · 81 lines · 39 tokens per session scan A b68cb4d54a4b
bcs-coordination is a skill published in the GitHub repository inclusionAI/Avernet (540 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 655 once invoked, about $0.0002 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
coordinate-agents
Route Codex-native multi-agent orchestration in a Git repository through a local-first, recoverable Agent Bus. Use for role-based planning, task execution, review, recovery, adapters, and human-gated release workflows. The plugin supports Codex CLI, Google Antigravity CLI, Claude, and other configured coding agents.…
coordinate-task
Run a Coordinate Agents Task from requirement clarification through planning, implementation, review, and the human release gate. Hide Agent Bus transport details behind the durable Task API.
coordinate-recover
Diagnose and safely resume Coordinate Agents Tasks after executable failure, non-zero exit, timeout, stale claim, processing message, or Implementer ERROR. Recovery is explicit and never an automatic retry loop.
coordinate-setup
Discover coding CLIs on the current computer and configure a Coordinate Agents implementation agent. Use for setup, executable checks, registered agents, user-level configuration, and project-over-user precedence.
coordinate-review
Review a Coordinate Agents implementation as the Codex Reviewer. Verify the real commit, diff, tests, validation evidence, and specification without modifying the Implementer's product code.
deliberated-review
Review code with multiple specialist subagents, then use gemot to find where they disagree and why. Requires gemot MCP server configured.