status

A command that reports the current state of a Network-AI swarm, a group of cooperating AI agents, using its shared board, token budget, and audit history.

In plain words
What is it for?
Use it to inspect shared status and task data, check remaining federated tokens, and review the ten most recent audit entries.
Why use it?
It gathers the main operational details in one concise report and highlights unusual activity such as denied permissions or stale state.

Command

Install

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.

agentmods
npx agentmods add commands/jovancoding/network-ai/status
Clone the repo
git clone --depth 1 https://github.com/Jovancoding/Network-AI
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 146 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.00146
Opus 5 $0.00009 $0.00073
Sonnet 5 $0.00003 $0.00029
Haiku 4.5 $0.00002 $0.00015

Measured 2d ago against content hash c6b95a1419b3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

status 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 2d 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.

commands/status.md · 12 lines

What it actually says

Give me a concise Network-AI swarm status report. Use the Network-AI MCP tools that are already loaded:

  1. Call blackboard_list to get the current shared-state keys, then blackboard_read on the most relevant ones (status, task, fsm keys).
  2. Call budget_status for the federated token budget.
  3. Call audit_query for the 10 most recent audit entries.

Summarize in three short sections: Blackboard, Budget, Recent activity. Flag anything unusual (denied permissions, budget near ceiling, stale state).

Changes

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.

  1. 2d ago First seen · 12 lines · 17 tokens per session scan A c6b95a1419b3

Subscribe to this mod's changes

status is a command published in the GitHub repository Jovancoding/Network-AI (72 stars, last pushed 8d ago), licensed MIT. It adds 17 tokens to every session and 146 once invoked, about $0.0001 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.