init

A setup command that creates three planning files for a complex software feature: a task plan, a findings file, and a progress file.

In plain words
What is it for?
Use it at the beginning of a complex feature to initialize planning documents in the repository’s root directory.
Why use it?
It gives a project a consistent place to track planned work, discoveries, and current status before development starts.

Command

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/littlestudent886/complex-dev-skills/init
Clone the repo
git clone --depth 1 https://github.com/littlestudent886/complex-dev-skills
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 184 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.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.00184
Opus 5 $0.00009 $0.00092
Sonnet 5 $0.00003 $0.00037
Haiku 4.5 $0.00002 $0.00018

Measured 2d ago against content hash a81967bde245, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

claude/plugins/complex-feature-dev/commands/init.md · 19 lines

What it actually says

Initialize Planning Files

Create the 3 planning files in the project root (git repo root by default):

  • task_plan.md
  • findings.md
  • progress.md

Run the initializer:

Note: if you are in a bash environment (Git Bash/MSYS/WSL), prefer the bash command even on Windows.

  • macOS/Linux (or Windows Git Bash): bash "$(ls -dt ~/.claude/plugins/cache/complex-dev-skills/complex-feature-dev/*/scripts/init-session.sh 2>/dev/null | head -1)"
  • Windows PowerShell: pwsh -ExecutionPolicy Bypass -File "~/.claude/plugins/cache/complex-dev-skills/complex-feature-dev/<version>/scripts/init-session.ps1"

Confirm the files exist, then stop.

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. 2d ago First seen · 19 lines · 17 tokens per session scan A a81967bde245

Subscribe to this mod's changes

init is a command published in the GitHub repository littlestudent886/complex-dev-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 184 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.