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/cdeust/ai-architect-mcpWrote 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/cdeust/ai-architect-mcp/check-status)<a href="https://agentmods.dev/commands/cdeust/ai-architect-mcp/check-status"><img src="https://agentmods.dev/badge/commands/cdeust/ai-architect-mcp/check-status.svg" alt="Measured on agentmods" 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.00144 |
| Opus 5 | $0.00008 | $0.00072 |
| Sonnet 5 | $0.00003 | $0.00029 |
| Haiku 4.5 | $0.00002 | $0.00014 |
Grade A, and why
check-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 7d 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
Check Status
Step 1 — Load pipeline state
ai_architect_load_session_state(session_id="current")
Step 2 — Report
Display the current pipeline state:
- Current stage (0-10 or "complete")
- Active finding ID
- Retry count
- Context budget usage
ai_architect_check_context_budget()
ai_architect_query_audit_events(filter={"type": "stage_transition"}, limit=10)
Report the last 10 stage transitions and current position in the pipeline.
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.
- 7d ago First seen · 29 lines · 15 tokens per session scan A 7df6819afa6e
check-status is a command published in the GitHub repository cdeust/ai-architect-mcp (1 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 144 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-31.
Other commands, from other repositories
release
Create a new release with version bump, changelog update, git tag, npm publish, and optional GitHub Release.
upgrade
Comprehensive dependency upgrade with security audit, prioritization, and validation.
api
Debug API and data flow issues by tracing through Component -> TanStack Query -> Express Route -> Service -> SQLite/JSONL.
reconcile
Check developer guides for documentation drift against recent code changes.
performance
Diagnose performance issues including slow renders, bundle size, N+1 queries, and memory leaks.
learn
Learn new capabilities through experimentation, then codify into the system.