agentweaver: Command for Claude Code

.specify/extensions/squad/commands/init.md

init is a command for Claude Code from sabbour/agentweaver. It costs 12 tokens per session (1,090 once invoked), scanned A, original, MIT.

A setup command that reads an implementation plan and creates a Squad team matched to the project's technology, architecture, and work phases.

In plain words
What is it for?
Use it after creating a plan to set up specialized Squad agents and their work-routing rules.
Why use it?
It avoids building a generic team that does not fit the project. It also checks that the required plan exists before starting.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is sabbour/agentweaver's own configuration. It tells Claude Code how to work on agentweaver itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentweaver configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/sabbour/agentweaver/dev/.specify/extensions/squad/commands/init.md
Clone the repo
git clone --depth 1 https://github.com/sabbour/agentweaver

Made for: Claude Code.

Wrote 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.

agentmods badge for init

README.md
[![agentmods](https://agentmods.dev/badge/commands/sabbour/agentweaver/init/github.svg)](https://agentmods.dev/commands/sabbour/agentweaver/init)
Your own site
<a href="https://agentmods.dev/commands/sabbour/agentweaver/init"><img src="https://agentmods.dev/badge/commands/sabbour/agentweaver/init/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.

agentmods 80×15 button for init

Your own site · 80×15
<a href="https://agentmods.dev/commands/sabbour/agentweaver/init"><img src="https://agentmods.dev/badge/commands/sabbour/agentweaver/init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,090 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.01090
Opus 5.5 $0.00005 $0.00436
Sonnet 5.5 $0.00002 $0.00218
Haiku 4.5 $0.00001 $0.00109

Measured 1mo ago against content hash 920ce5321884, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

init 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.

.specify/extensions/squad/commands/init.md · 117 lines

How it starts

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

Squad Bridge: Init

Read the implementation plan and bootstrap a Squad team tailored to its technology stack, architecture layers, and implementation phases. Run this once after your initial /speckit.plan to get a squad that mirrors your project's concrete technical shape.

Why plan and not spec? The spec (spec.md) is intentionally tech-agnostic — it captures goals, users, and constraints. The plan (plan.md) is where concrete technology decisions live (e.g., "React 19 with Next.js", "Go API with gin"). Generating agents from the plan produces sharper charters with accurate capabilities and routing rules.

Prerequisites

Verify Squad CLI is available:

squad --version

If that fails, install it first:

npm install -g @bradygaster/squad-cli

User Input

$ARGUMENTS

Steps

  1. Read the plan from the active spec directory under specs/ (e.g., specs/001-<name>/plan.md). If no plan exists, tell the user to run /speckit.plan first and stop. Also read spec.md for supplementary context (goals, constraints, non-functional requirements).

  2. Read tasks from specs/<id>/tasks.md if it exists (used to infer work types and routing signals).

  3. Load bridge config from .specify/extensions/squad/squad-config.yml if it exists, otherwise use extension defaults.

  4. Analyze the plan to extract:

    • Technology stack explicitly chosen (e.g., "React 19 with Next.js", "Go microservices with gin", "PostgreSQL with Prisma ORM")
    • Architecture layers (frontend, backend, API gateway, data layer, infra)
    • Implementation phases (if the plan defines phased delivery)
    • Cross-cutting concerns (e.g., auth, testing, documentation, CI/CD)
    • Any explicit roles or team structure mentioned in the plan or spec
  5. Initialize Squad if .squad/ does not already exist:

    squad init
    
  6. Generate agent definitions — for each identified domain/concern, create a Squad agent with:

    • A descriptive name (e.g., backend-engineer, frontend-engineer)
    • A role derived from the domain
    • capabilities array (name + level: expert/proficient/basic) inferred from how prominently the domain features in the plan
    • model set to the tier from config that matches the agent's complexity
    • status: active

Read the full file on GitHub · 117 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.

  1. 1mo ago First seen · 117 lines · 12 tokens per session scan A 920ce5321884

Subscribe to this mod's changes

init is a command published in the GitHub repository sabbour/agentweaver (7 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 1,090 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.