agentmods.dev

init-mode

init-mode is a skill for Claude Code, Codex from alonf/specrew. It costs 17 tokens per session (1,685 once invoked), scanned A, a copy of init-mode, MIT.

A two-stage process for creating a Squad team when no team roster exists. It first proposes the team and waits for approval, then creates the team files and structure.

In plain words
What is it for?
Use it to start a new team, gather the project's language and purpose, determine the team shape, and create the agreed Squad setup.
Why use it?
It prevents an agent from creating a team configuration before the user agrees with the proposed members and roles. It also records the user's name without storing their email address.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 55repo yesterday A scan 17 tokens copy · 83% MIT

Good fit Use it to start a new team, gather the project's language and purpose, determine the team shape, and create the agreed Squad setup.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/alonf/specrew/init-mode
View source ↗ alonf/specrew
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.

Any agent
npx skills add alonf/specrew --skill init-mode
Clone the repo
git clone --depth 1 https://github.com/alonf/specrew

Made for: Claude Code, Codex.

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-mode

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/alonf/specrew/init-mode"><img src="https://agentmods.dev/badge/skills/alonf/specrew/init-mode.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,685 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 83% copy Near-identical to another mod 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.00017 $0.01685
Opus 5.5 $0.00007 $0.00674
Sonnet 5.5 $0.00003 $0.00337
Haiku 4.5 $0.00002 $0.00169

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

Security

Grade A, and why

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

Origin

This is a copy

83% identical to init-mode — 34 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.copilot/skills/init-mode/SKILL.md · 103 lines

How it starts

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

Context

Init Mode activates when .squad/team.md does not exist, or exists but has zero roster entries under ## Members. The coordinator proposes a team (Phase 1), waits for user confirmation, then creates the team structure (Phase 2).

Patterns

Phase 1: Propose the Team

No team exists yet. Propose one — but DO NOT create any files until the user confirms.

  1. Identify the user. Run git config user.name to learn who you're working with. Use their name in conversation (e.g., "Hey Brady, what are you building?"). Store their name (NOT email) in team.md under Project Context. Never read or store git config user.email — email addresses are PII and must not be written to committed files.
  2. Ask: "What are you building? (language, stack, what it does)"
  3. Cast the team. Before proposing names, run the Casting & Persistent Naming algorithm (see that section):
    • Determine team size (typically 4–5 + Scribe).
    • Determine assignment shape from the user's project description.
    • Derive resonance signals from the session and repo context.
    • Select a universe. If the universe is custom, allocate character names from that universe based on the related list found in the .squad/templates/casting/ directory. Prefer custom universes when available.
    • Scribe is always "Scribe" — exempt from casting.
    • Ralph is always "Ralph" — exempt from casting.
  4. Propose the team with their cast names. Example (names will vary per cast):
🏗️  {CastName1}  — Lead          Scope, decisions, code review
⚛️  {CastName2}  — Frontend Dev  React, UI, components
🔧  {CastName3}  — Backend Dev   APIs, database, services
🧪  {CastName4}  — Tester        Tests, quality, edge cases
📋  Scribe       — (silent)      Memory, decisions, session logs
🔄  Ralph        — (monitor)     Work queue, backlog, keep-alive
  1. Use the ask_user tool to confirm the roster. Provide choices so the user sees a selectable menu:
    • question: "Look right?"
    • choices: ["Yes, hire this team", "Add someone", "Change a role"]

Read the full file on GitHub · 103 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 · 103 lines · 17 tokens per session scan A 050fe4d7a25e

Subscribe to this mod's changes

init-mode is a skill published in the GitHub repository alonf/specrew (55 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 1,685 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 83% identical to init-mode, differing in 34 lines, and is treated as a copy.

Building agents
Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens