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.
git clone --depth 1 https://github.com/secureagentics/AdrianWrote 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/commands/secureagentics/adrian/adrian-status)<a href="https://agentmods.dev/commands/secureagentics/adrian/adrian-status"><img src="https://agentmods.dev/badge/commands/secureagentics/adrian/adrian-status/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/commands/secureagentics/adrian/adrian-status"><img src="https://agentmods.dev/badge/commands/secureagentics/adrian/adrian-status.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.00015 | $0.00219 |
| Opus 5.5 | $0.00006 | $0.00088 |
| Sonnet 5.5 | $0.00003 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
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 2mo 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.
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.
- 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'
- 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.
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.
- 2mo ago First seen · 21 lines · 15 tokens per session scan A b0740fd8b2f3
adrian-status is a command published in the GitHub repository secureagentics/Adrian (586 stars, last pushed 9d ago), licensed Apache-2.0. It adds 15 tokens to every session and 219 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-swarm
Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment.
examples
Real-world examples and scenarios for pair programming sessions.
issue-tracker
Intelligent issue management and project coordination with ruv-swarm integration for automated tracking, progress monitoring, and team coordination.
config
Complete configuration guide for pair programming sessions.
start
Start a new pair programming session with AI assistance.