adrian-status

A command that reports Adrian's security-service configuration and connection health without revealing the API key. It checks the backend address, whether a key exists, and whether authentication works.

In plain words
What is it for?
Use it to check the configured backend, confirm key presence safely, run the connection test, and identify the initialization command if setup is incomplete.
Why use it?
It removes guesswork when Adrian commands fail because the service is unreachable or credentials are missing.

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/secureagentics/adrian/adrian-status
Clone the repo
git clone --depth 1 https://github.com/secureagentics/Adrian
Per session 15 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.00015 $0.00219
Opus 5 $0.00008 $0.00110
Sonnet 5 $0.00003 $0.00044
Haiku 4.5 $0.00002 $0.00022

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

Security

Grade A, and why

adrian-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.

integrations/claude-code/commands/adrian-status.md · 21 lines

What it actually says

Report the current Adrian configuration and whether it can reach the backend. NEVER print, cat, or echo the API key value or the .env contents.

  1. Show the effective backend URL and whether a key is set (boolean only):
grep -E '^ADRIAN_WS_URL=' ~/.adrian/.env 2>/dev/null || echo 'ADRIAN_WS_URL not set (default ws://localhost:8080/ws)'
grep -Eq '^ADRIAN_API_KEY=adr_(live|local)_.+' ~/.adrian/.env && echo 'API key: set' || echo 'API key: NOT set'
  1. Check connectivity + auth (prints OK/FAIL + backend mode, never the key):
adrian-python -m adrian_cc.agent verify

Report its output verbatim.

If the key is missing or verify FAILs, suggest running /adrian-cc:adrian-init.

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 · 21 lines · 15 tokens per session scan A b0740fd8b2f3

Subscribe to this mod's changes

adrian-status is a command published in the GitHub repository secureagentics/Adrian (555 stars, last pushed 12d ago), licensed Apache-2.0. It adds 15 tokens to every session and 219 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.