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/AhmedHabiba/architorWrote 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/ahmedhabiba/architor/status)<a href="https://agentmods.dev/commands/ahmedhabiba/architor/status"><img src="https://agentmods.dev/badge/commands/ahmedhabiba/architor/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/ahmedhabiba/architor/status"><img src="https://agentmods.dev/badge/commands/ahmedhabiba/architor/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.00000 | $0.00433 |
| Opus 5 | $0.00000 | $0.00217 |
| Sonnet 5 | $0.00000 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00043 |
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 8d 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
Read .arch/state.json and display a comprehensive status report.
Format the output as:
ARCHITECTURE AGENT — PROJECT STATUS
Project: [project_name]
Started: [created_at]
Current Phase: Phase [N] — [Name]
Phase 1: Evaluation [Accepted / In Progress / Not Started]
Phase 2: Methodology
2A Pattern: [Accepted / Awaiting Acceptance / Not Started]
2B Component Map: [Accepted / Awaiting Acceptance / Not Started]
2C Cross-Cutting: [Accepted / Awaiting Acceptance / Not Started]
Phase 3: Components [X of Y / Not Started]
Phase 4: Finalization [Not Started]
Reopens: [count] of [max] used
Decisions: [decision_count]
If in Phase 3, show component breakdown:
Component Progress:
[status] 1. API Gateway — Accepted
[status] 2. Auth Service — Accepted
[status] 3. Core Database — Accepted
[status] 4. Message Queue — Awaiting Acceptance <- CURRENT
[status] 5. Notification Service — Pending
[status] 6. Analytics Engine — Pending
[status] 7. CDN / Static Assets — Pending
Use these status indicators:
- Accepted: check mark
- In Progress / Awaiting Acceptance: in progress indicator
- Pending: empty indicator
- Needs Review: warning indicator (after a reopen)
Also show:
- Architecture pattern: [if decided]
- Org context source: [file / interview / assumed / not loaded]
- Open gaps/risks from Phase 1: [count]
- Key files generated: [list of .arch files that exist]
If there's a pending action, prompt the user: "Next action: [what the user should do next, e.g., 'Run /accept to accept the current component, or /refine to request changes']"
$ARGUMENTS
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.
- 8d ago First seen · 52 lines · 0 tokens per session scan A 74a8c84f9b26
status is a command published in the GitHub repository AhmedHabiba/architor (6 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 433 tokens. 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
octo-schedule
Manage scheduled workflow jobs for the Claude Octopus scheduler.
octo-scheduler
Manage the Claude Octopus scheduled workflow runner daemon.
discover
Run a full product discovery cycle — from outcome definition through opportunity mapping, prioritisation, and experiment design. Use when the team isn't sure what to build next, or before writing a PRD for a complex feature space.
specmanager-build
Build one phase of a SpecManager feature's plan via the builder subagent. Stops at the phase boundary; never advances.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
linear-bulk
Apply the same change to many Linear issues at once. Dry-run by default.