A command that rebuilds Squad agent definitions from the current Speckit implementation plan. Squad is the project's team of specialized coding agents.

Use it after changing a plan to update agent definitions and flag agents the new plan no longer supports.

It keeps agents, their capabilities, and task-routing rules aligned when the plan changes, without deleting older agents.

generate — 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/generate

Clone the repo

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

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

When invoked 683 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.00010	$0.00683
Opus 5	$0.00005	$0.00342
Sonnet 5	$0.00002	$0.00137
Haiku 4.5	$0.00001	$0.00068

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

Security

Grade A, and why

generate 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/generate.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Squad Bridge: Generate

Re-read the implementation plan and regenerate Squad agent definitions, capabilities, and routing rules to stay in sync with plan changes. Safe to run repeatedly — existing agents are updated in place; agents no longer supported by the plan are flagged (not deleted).

This command is also triggered by the after_plan hook.

User Input

$ARGUMENTS

Steps

Verify .squad/ exists — if not, tell the user to run /speckit.squad.init first and stop.
Read the plan from the active spec directory under specs/ (e.g., specs/001-<name>/plan.md). Also read spec.md for supplementary context (goals, constraints).
Load bridge config from .specify/extensions/squad/squad-config.yml if it exists, otherwise use extension defaults.
Read existing agents from .squad/agents/ (each agent lives in .squad/agents/{name}/charter.md) so changes can be diffed rather than blindly overwritten. Preserve history.md files (accumulated project knowledge — never touch these).
Analyze the plan to extract technology stack, architecture layers, implementation phases, and cross-cutting concerns (same logic as init). If $ARGUMENTS names a specific domain, limit regeneration to that domain's agent.
Diff against existing agents:
- New domains found in plan but no matching agent → create new agent
- Changed domains (different prominence or tech stack) → update agent capabilities and model tier
- Removed domains (in existing agents but absent from new plan) → set status: inactive and note in output (do NOT delete)
Update squad.config.ts at the project root (using defineSquad() with defineTeam(), defineAgent(), and defineRouting()) to reflect the new agent set, routing rules, and model tier assignments.
Update .squad/routing.md to add routing rules for any new agents and update patterns for changed agents.
Print a diff summary:

Read the full file on GitHub · 73 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 · 73 lines · 10 tokens per session scan A 3443f6f593f8

Subscribe to this mod's changes

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

Building agents agent-orchestration ai-agents aks dotnet human-in-the-loop kubernetes

blackboard

Read or write a Network-AI blackboard key (shared multi-agent state).

Jovancoding/Network-AI · 16 tokens

self-improve

Bootstrap and operate a self-improving agent workspace. Scaffolds .learnings/ and memory/ directories, captures errors and learnings during a session, detects recurring patterns, and promotes stable entries to project memory (CLAUDE.md, AGENTS.md, or references/). Also implements the Proactive Agent pillars — WAL…

nitinjain999/platform-skills · 137 tokens

generate