A health-check command that compares the project specification, task list, and Squad agents. It shows which technical areas have an active agent and which work has no coverage.

Use it before a work session or after a specification change to check whether the planned work is assigned to suitable agents.

It reveals gaps, unrouted tasks, and inactive agents before they cause missed work.

status — Command by sabbour

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/sabbour/agentweaver/status

Clone the repo

git clone --depth 1 https://github.com/sabbour/agentweaver

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 713 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.

Model	Per session	Once invoked
Fable 5	$0.00011	$0.00713
Opus 5	$0.00005	$0.00357
Sonnet 5	$0.00002	$0.00143
Haiku 4.5	$0.00001	$0.00071

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

Security

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

.specify/extensions/squad/commands/status.md · 87 lines

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

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.md exists), 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
────────────────────────────────────────

Read the full file on GitHub · 87 lines

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.

2d ago First seen · 87 lines · 11 tokens per session scan A cf35a41f2b0a

Subscribe to this mod's changes

status is a command published in the GitHub repository sabbour/agentweaver (5 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 713 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.

Data and AI DevOps and cloud Testing agent-orchestration ai-agents aks dotnet human-in-the-loop kubernetes

cost-tracker

Track session costs, understand token spend, and get optimization tips.

rohitg00/pro-workflow · 12 tokens

journey-audit

Outside-in product audit as a deep session — 7 read-only roles check what the site promises against what the code does, what a user experiences, what arrives by mail, and what the data says is used. Writes a dossier; needs a per-repo journey-manifest.

Kanevry/session-orchestrator · 56 tokens

status