Borrowing it
Nothing to install: this file belongs to sabbour/agentweaver. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sabbour/agentweaver/dev/.specify/extensions/squad/commands/status.mdgit clone --depth 1 https://github.com/sabbour/agentweaverWrote 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/sabbour/agentweaver/status)<a href="https://agentmods.dev/commands/sabbour/agentweaver/status"><img src="https://agentmods.dev/badge/commands/sabbour/agentweaver/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/sabbour/agentweaver/status"><img src="https://agentmods.dev/badge/commands/sabbour/agentweaver/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.00011 | $0.00713 |
| Opus 5.5 | $0.00004 | $0.00285 |
| Sonnet 5.5 | $0.00002 | $0.00143 |
| Haiku 4.5 | $0.00001 | $0.00071 |
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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Squad Bridge: Status
Cross-reference the Speckit spec, task list, and Squad team to surface coverage gaps, unrouted work, and idle agents. Useful as a health check before starting a session or after a spec change.
User Input
$ARGUMENTS
Steps
-
Load all artifacts:
- Spec:
specs/<id>/spec.md - Tasks:
specs/<id>/tasks.md(if exists) - Squad agents:
.squad/agents/— each agent in.squad/agents/{name}/charter.md(if exists) - Squad routing:
.squad/routing.md(if exists) - Bridge config:
.specify/extensions/squad/squad-config.yml
- Spec:
-
Check: Spec domains vs. agent coverage
For each technology domain and concern identified in the spec, determine whether an active Squad agent covers it:
Domain Coverage ────────────────────────────────────────────── Domain Agent Status ────────────────────────────────────────────── REST API / Node.js backend-engineer ✅ covered React / TypeScript frontend-engineer ✅ covered PostgreSQL data-engineer ✅ covered CI/CD / DevOps (none) ⚠️ gap Mobile (iOS) mobile-engineer ⚠️ inactive ────────────────────────────────────────────── -
Check: Tasks vs. routing
For each task (if
specs/<id>/tasks.mdexists), verify it can be routed to an active agent via the current routing rules:Task Routing Coverage ───────────────────────────────────────────────────── Total tasks : 12 Routable tasks : 10 ✅ Unroutable tasks : 2 ⚠️ (run /speckit.squad.route) ───────────────────────────────────────────────────── -
Check: Agent utilization
List active agents and flag any with no tasks mapped to them:
Agent Utilization ──────────────────────────────────────── Agent Tasks Status ──────────────────────────────────────── backend-engineer 5 ✅ active frontend-engineer 4 ✅ active qa-engineer 3 ✅ active data-engineer 0 ⚠️ no tasks assigned ────────────────────────────────────────
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.
- 1mo ago First seen · 87 lines · 11 tokens per session scan A cf35a41f2b0a
status is a command published in the GitHub repository sabbour/agentweaver (7 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 713 once invoked, about $0.0000 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-31.
Other commands, from other repositories
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
dashboard-session-hide
Hide a session from the dashboard list. Usage /dashboard:session-hide.
research-close
Close research - moves to done.
aigon-feedback-triage
Run a triage loop for one feedback item with explicit human confirmation before writes.
factory-ticket
Implement exactly one already-claimed Linear ticket in the current worktree.
ah
Show Aigon commands (shortcut for help).