init

A setup workflow for initializing PlanKit, a project-planning folder structure, for the first time. It checks existing files, reports the current state, and can migrate planning documents.

In plain words
What is it for?
Use it to inspect or create PlanKit, count existing ideas and missions, choose whether to migrate documents, and prepare the project for other PlanKit workflows.
Why use it?
It prevents an existing planning setup from being overwritten unknowingly and establishes the project's naming and storage conventions.

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/flinedev/plankit/init
Clone the repo
git clone --depth 1 https://github.com/FlineDev/PlanKit
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 2,638 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.00000 $0.02638
Opus 5 $0.00000 $0.01319
Sonnet 5 $0.00000 $0.00528
Haiku 4.5 $0.00000 $0.00264

Measured 2d ago against content hash 5879d7f9a1d9, 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.

commands/init.md · 294 lines

How it starts

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

Setup — First-time project initialization with migration

You are initializing PlanKit for this project. Follow these steps exactly.

Step 1: Check Existing State

Check if a PlanKit folder already exists:

  • Look for PlanKit/ in the project root
  • Look for plan-kit/ in the project root

If a PlanKit folder exists:

  • Read .config.json from it
  • Count files and approximate word counts in Ideas, Roadmap, Features
  • Display current state:
    ════════════════════════════════════════════════════════════════
    📋 PlanKit already initialized
    ════════════════════════════════════════════════════════════════
    
    Folder: [PlanKit/ or plan-kit/]
    Convention: [UpperCamelCase or kebab-case]
    Ideas: [N words across M themes]
    Roadmap: [N features across M versions]
    Features: [N mission files]
    
    ════════════════════════════════════════════════════════════════
    
  • Use AskUserQuestion:
    {
      "questions": [{
        "question": "PlanKit is already set up. What would you like to do?",
        "header": "Action",
        "options": [
          {"label": "Re-run migration", "description": "Import additional planning documents into existing PlanKit"},
          {"label": "Nothing, exit", "description": "Keep current setup as-is"}
        ],
        "multiSelect": false
      }]
    }
    
  • If "Nothing" → exit with a brief "All good!" message.
  • If "Re-run migration" → skip to Step 4.

If no PlanKit folder exists → continue to Step 2.

Step 2: Detect Naming Convention

Scan the project root directory to detect the naming convention:

UpperCamelCase indicators (Swift/Apple ecosystem):

  • Sources/, Tests/, Models/, Views/, ViewModels/
  • .xcodeproj, .xcworkspace, Package.swift
  • Resources/, Extensions/, Helpers/, Protocols/

kebab-case indicators (JS/web ecosystem):

  • src/, lib/, dist/, node_modules/
  • package.json, tsconfig.json, webpack.config.js
  • public/, assets/, components/

If clear match → use detected convention, tell user: "Detected [convention] based on project structure."

Read the full file on GitHub · 294 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. 2d ago First seen · 294 lines · 0 tokens per session scan A 5879d7f9a1d9

Subscribe to this mod's changes

init is a command published in the GitHub repository FlineDev/PlanKit (20 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,638 tokens. 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-30.