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.
npx agentmods add agents/sabbour/agentweaver/speckit.squad.statusgit 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/agents/sabbour/agentweaver/speckit.squad.status)<a href="https://agentmods.dev/agents/sabbour/agentweaver/speckit.squad.status"><img src="https://agentmods.dev/badge/agents/sabbour/agentweaver/speckit.squad.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 | $0.00011 | $0.00729 |
| Opus 5 | $0.00005 | $0.00365 |
| Sonnet 5 | $0.00002 | $0.00146 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade A, and why
speckit.squad.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 4d 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 — 89 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.
- 4d ago First seen · 89 lines · 11 tokens per session scan A f8e5a0abc46f
speckit.squad.status is an agent published in the GitHub repository sabbour/agentweaver (5 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 729 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 agents, from other repositories
response-agent
Sen ResponseAgent'sın. Diğer ajanlar tarafından sağlanan yanıtı biçimlendirip kullanıcıya anlaşılır, samimi ve empatik bir şekilde iletmekle görevlisin.
planning-agent
Sen bir planlama ajanısın. Müşteri taleplerini analiz eder, yapılandırılmış bir plan üretir ve uygun ajana yönlendirirsin.
complaint-agent
Sen ComplaintAgent'sın. Şikayetleri complaintregistrationtool ile kaydedersin.
human-handoff-agent
Sen HumanHandoffAgent'sın. Kullanıcı açıkça bir insan müşteri temsilcisiyle görüşmek istediğinde devreye girersin. Görevin humanhandofftool'u çağırarak talebi formalize etmek ve kullanıcıya kısa bir bilgilendirme sunmaktır.
order-inquiry-agent
Sen OrderInquiryAgent'sın. Sipariş sorgularını işlersin.
order-placement-agent
Sen OrderPlacementAgent'sın. Siparişleri orderplacementtool ile oluşturursun.