status

A command that checks whether the AI providers used by claude-council are available and correctly configured. It reports connection state, response time, model name, and suggested fixes.

In plain words
What is it for?
Use it to check provider connectivity and configuration, see which models are active, and review any background council jobs.
Why use it?
It shows which providers can currently answer requests before you try to use the council. This makes missing keys, timeouts, and authentication errors easier to find.

Command

Part of the claude-council plugin — 4 skills, 3 commands, 1 agent, 1 hook shipped together

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/hex/claude-council/status
Clone the repo
git clone --depth 1 https://github.com/hex/claude-council

Or install claude-council, the plugin that ships this one along with the rest of its 4 skills, 3 commands, 1 agent, 1 hook.

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 219 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.00009 $0.00219
Opus 5 $0.00005 $0.00110
Sonnet 5 $0.00002 $0.00044
Haiku 4.5 $0.00001 $0.00022

Measured 3d ago against content hash 20259f70c291, 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 3d 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 · 37 lines

What it actually says

Check the status of all configured AI providers.

Execution

Run the status check script:

bash ${CLAUDE_PLUGIN_ROOT}/scripts/check-status.sh

Output

Present the script output directly - it includes formatted status for each provider:

  • Connection status (connected, timeout, auth error, not configured)
  • Response time in milliseconds
  • Configured model name
  • Per-provider fix command for anything not available
  • Summary of available providers

No additional formatting needed - the script handles all presentation.

Background Jobs

Also list any background council jobs:

bash ${CLAUDE_PLUGIN_ROOT}/scripts/run-council.sh --jobs

If the output is non-empty, present it as a table (job id, status, created) and mention /claude-council:result <job-id>. If empty, omit the section.

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. 3d ago First seen · 37 lines · 9 tokens per session scan A 20259f70c291

Subscribe to this mod's changes

status is a command published in the GitHub repository hex/claude-council (673 stars, last pushed 7d ago), licensed MIT. It adds 9 tokens to every session and 219 once invoked, about $0.0000 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.