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.rungit 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.run)<a href="https://agentmods.dev/agents/sabbour/agentweaver/speckit.squad.run"><img src="https://agentmods.dev/badge/agents/sabbour/agentweaver/speckit.squad.run.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.00007 | $0.01173 |
| Opus 5 | $0.00003 | $0.00587 |
| Sonnet 5 | $0.00001 | $0.00235 |
| Haiku 4.5 | $0.00001 | $0.00117 |
Grade A, and why
speckit.squad.run 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 3d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Squad Bridge: Run
Execute routed tasks by spawning Squad agent sessions. Reads the task list
and agent assignments produced by /speckit.squad.route, then launches
agents to do the work — creating branches, running sessions, and optionally
creating PRs.
This is the command that closes the loop: specs become plans, plans become tasks, tasks get routed to agents, and this command makes agents execute.
Prerequisites
- Tasks must be routed: run
/speckit.squad.route --update-tasksfirst - Squad CLI available:
squad --version - GitHub CLI authenticated:
gh auth status
User Input
$ARGUMENTS
Steps
-
Read tasks from
specs/<id>/tasks.md. Identify tasks that have squad routing metadata (comments like<!-- squad:agent=backend-engineer tier=standard -->). If no routed tasks found, tell the user to run/speckit.squad.route --update-tasksfirst and stop. -
Load Squad agents from
.squad/agents/and verify each assigned agent exists and hasstatus: active. -
Load bridge config from
.specify/extensions/squad/squad-config.ymlif it exists, otherwise use extension defaults. -
Parse arguments:
- No args: run all pending routed tasks
- Task ID or title fragment (e.g.,
task-03): run only that task --dry-run: show what would execute without starting sessions--retry: re-run previously failed tasks only--retry <task-id>: re-run a specific failed task
-
If
--dry-run, print the execution plan and stop:Dry Run — would execute: ───────────────────────────────────────────────────────── Task Agent Tier ───────────────────────────────────────────────────────── Design REST API endpoints backend-engineer full Implement JWT authentication backend-engineer standard Build login form component frontend-engineer standard Write unit tests for auth qa-engineer standard ───────────────────────────────────────────────────────── 4 tasks | 3 agents | parallel limit: 3 Run without --dry-run to execute.
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.
- 3d ago First seen · 136 lines · 7 tokens per session scan A 13f3b92e360f
speckit.squad.run is an agent published in the GitHub repository sabbour/agentweaver (5 stars, last pushed today), licensed MIT. It adds 7 tokens to every session and 1,173 once invoked, about $0.0000 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.