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 commands/sabbour/agentweaver/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/commands/sabbour/agentweaver/run)<a href="https://agentmods.dev/commands/sabbour/agentweaver/run"><img src="https://agentmods.dev/badge/commands/sabbour/agentweaver/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.01157 |
| Opus 5 | $0.00003 | $0.00579 |
| Sonnet 5 | $0.00001 | $0.00231 |
| Haiku 4.5 | $0.00001 | $0.00116 |
Grade A, and why
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 — 134 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 · 134 lines · 7 tokens per session scan A 13c717a6c912
run is a command published in the GitHub repository sabbour/agentweaver (5 stars, last pushed 3d ago), licensed MIT. It adds 7 tokens to every session and 1,157 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 commands, from other repositories
cost-tracker
Track session costs, understand token spend, and get optimization tips.
syncblk
Displays information about synchronization blocks (thin locks and System.Threading.Monitor instances). Useful for diagnosing deadlocks and contention issues.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.
wb-notify
Load directions via mcpwork-buddywbrun("agentdocs", {"path": "notifications/notify-directions", "depth": "full"}), then call the capability.
goal
Open a /goal contract — write a verifiable manifest before dispatching work.
speckit.taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.