pre-task

A preparation command that loads context and plans support for a new coding task before work starts.

In plain words
What is it for?
Use it to load previous decisions and task context, automatically start suitable agents, choose a coordination structure, or estimate task complexity.
Why use it?
It reduces repeated setup by restoring relevant past information and estimating what the task may require.

Command for Claude Code

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/f-amine/vibe-stack/pre-task
Clone the repo
git clone --depth 1 https://github.com/f-amine/vibe-stack

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 530 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% 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 $0.00000 $0.00530
Opus 5 $0.00000 $0.00265
Sonnet 5 $0.00000 $0.00106
Haiku 4.5 $0.00000 $0.00053

Measured yesterday against content hash 93597737b83e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pre-task 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 yesterday.

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

100% identical to pre-task — 0 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.

.claude/commands/hooks/pre-task.md · 112 lines

How it starts

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

hook pre-task

Execute pre-task preparations and context loading.

Usage

npx claude-flow hook pre-task [options]

Options

  • --description, -d <text> - Task description for context
  • --auto-spawn-agents - Automatically spawn required agents (default: true)
  • --load-memory - Load relevant memory from previous sessions
  • --optimize-topology - Select optimal swarm topology
  • --estimate-complexity - Analyze task complexity

Examples

Basic pre-task hook

npx claude-flow hook pre-task --description "Implement user authentication"

With memory loading

npx claude-flow hook pre-task -d "Continue API development" --load-memory

Manual agent control

npx claude-flow hook pre-task -d "Debug issue #123" --auto-spawn-agents false

Full optimization

npx claude-flow hook pre-task -d "Refactor codebase" --optimize-topology --estimate-complexity

Features

Auto Agent Assignment

  • Analyzes task requirements
  • Determines needed agent types
  • Spawns agents automatically
  • Configures agent parameters

Memory Loading

  • Retrieves relevant past decisions
  • Loads previous task contexts
  • Restores agent configurations
  • Maintains continuity

Topology Optimization

  • Analyzes task structure
  • Selects best swarm topology
  • Configures communication patterns
  • Optimizes for performance

Complexity Estimation

  • Evaluates task difficulty
  • Estimates time requirements
  • Suggests agent count
  • Identifies dependencies

Integration

This hook is automatically called by Claude Code when:

  • Starting a new task
  • Resuming work after a break
  • Switching between projects
  • Beginning complex operations

Manual usage in agents:

# In agent coordination
npx claude-flow hook pre-task --description "Your task here"

Output

Returns JSON with:

{
  "continue": true,
  "topology": "hierarchical",
  "agentsSpawned": 5,
  "complexity": "medium",
  "estimatedMinutes": 30,
  "memoryLoaded": true
}

Read the full file on GitHub · 112 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. yesterday First seen · 112 lines · 0 tokens per session scan A 93597737b83e

Subscribe to this mod's changes

pre-task is a command published in the GitHub repository f-amine/vibe-stack (21 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 530 tokens. A static security scan graded it A with 0 findings. It is 100% identical to pre-task, differing in 0 lines, and is treated as a copy.