Borrowing it
Nothing to install: this file belongs to sabbour/agentweaver. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sabbour/agentweaver/dev/.specify/extensions/squad/commands/generate.mdgit 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/generate)<a href="https://agentmods.dev/commands/sabbour/agentweaver/generate"><img src="https://agentmods.dev/badge/commands/sabbour/agentweaver/generate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/sabbour/agentweaver/generate"><img src="https://agentmods.dev/badge/commands/sabbour/agentweaver/generate.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00010 | $0.00683 |
| Opus 5.5 | $0.00004 | $0.00273 |
| Sonnet 5.5 | $0.00002 | $0.00137 |
| Haiku 4.5 | $0.00001 | $0.00068 |
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 1mo 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 — 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.initfirst and stop. -
Read the plan from the active spec directory under
specs/(e.g.,specs/001-<name>/plan.md). Also readspec.mdfor supplementary context (goals, constraints). -
Load bridge config from
.specify/extensions/squad/squad-config.ymlif 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. Preservehistory.mdfiles (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$ARGUMENTSnames 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: inactiveand note in output (do NOT delete)
-
Update
squad.config.tsat the project root (usingdefineSquad()withdefineTeam(),defineAgent(), anddefineRouting()) to reflect the new agent set, routing rules, and model tier assignments. -
Update
.squad/routing.mdto add routing rules for any new agents and update patterns for changed agents. -
Print a diff summary:
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.
- 1mo ago First seen · 73 lines · 10 tokens per session scan A 3443f6f593f8
generate is a command published in the GitHub repository sabbour/agentweaver (7 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 683 once invoked, about $0.0000 per session on Opus 5.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
mach12:gh-pr-read
Read a GitHub pull request's title, body, and all top-level PR conversation comments; optionally locate an HTML-marker comment.
harness-onboarding
Generate a human-readable onboarding document from HARNESS.md, AGENTS.md, and REFLECTIONLOG.md — a friendly guide for new team members.
speckit.archive.run
Archive merged feature specs into project memory with provenance, sweep discovery, and gated cleanup.
qos-forge
Design a multi-agent team with Qualixar OS Forge. Provide a task description, Forge picks the topology, agents, and tools.
uninstall
Reverses the coordinator install, fully or back to marketplace.
trex.test.unit
Run unit tests against the package and command code (no database required).