opencode-kit: Agent for Claude Code

.opencode/agents/project-planner.md

project-planner is an agent for Claude Code, OpenCode from felipeslo/opencode-kit. It costs 37 tokens per session (3,430 once invoked), scanned A, a copy of project-planner, MIT.

Agent do planowania projektów programistycznych: dzieli prośbę na zadania, układa kolejność prac i przypisuje je odpowiednim agentom.

In plain words
What is it for?
Służy do planowania nowych projektów i większych funkcji, ustalania struktury plików oraz sprawdzania istniejącego kontekstu projektu.
Why use it?
Pomaga zamienić duże lub niejasne zadanie w plan, który można wykonać krok po kroku, z uwzględnieniem zależności między zadaniami.

Agent for Claude CodeOpenCode

Written for OpenCode and Claude Code: installed under .opencode/, but also a Claude Code subagent (agents/*.md). Also seen: mentions OpenCode.

This is felipeslo/opencode-kit's own configuration. It tells Claude Code and OpenCode how to work on opencode-kit 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 opencode-kit configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python .opencode/scripts/verify_all.py . --url http://localhost:3000.

Reuse

Borrowing it

Nothing to install: this file belongs to felipeslo/opencode-kit. 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/felipeslo/opencode-kit/main/.opencode/agents/project-planner.md
Clone the repo
git clone --depth 1 https://github.com/felipeslo/opencode-kit

Made for: Claude Code, OpenCode.

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 project-planner

README.md
[![agentmods](https://agentmods.dev/badge/agents/felipeslo/opencode-kit/project-planner/github.svg)](https://agentmods.dev/agents/felipeslo/opencode-kit/project-planner)
Your own site
<a href="https://agentmods.dev/agents/felipeslo/opencode-kit/project-planner"><img src="https://agentmods.dev/badge/agents/felipeslo/opencode-kit/project-planner/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 project-planner

Your own site · 80×15
<a href="https://agentmods.dev/agents/felipeslo/opencode-kit/project-planner"><img src="https://agentmods.dev/badge/agents/felipeslo/opencode-kit/project-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,430 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 91% 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.00037 $0.03430
Opus 5.5 $0.00015 $0.01372
Sonnet 5.5 $0.00007 $0.00686
Haiku 4.5 $0.00004 $0.00343

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

Security

Grade A, and why

project-planner 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

91% identical to project-planner — 194 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.

.opencode/agents/project-planner.md · 404 lines

How it starts

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

Project Planner - Smart Project Planning

You are a project planning expert. You analyze user requests, break them into tasks, and create an executable plan.

PHASE 0: CONTEXT CHECK (QUICK)

Check for existing context before starting:

  1. Read CODEBASE.md - Check OS field (Windows/macOS/Linux)
  2. Read any existing plan files in project root
  3. Check if request is clear enough to proceed
  4. If unclear: Ask 1-2 quick questions, then proceed

OS Rule: Use OS-appropriate commands!

  • Windows - Use Write tool for files, PowerShell for commands
  • macOS/Linux - Can use touch, mkdir -p, bash commands

PHASE -1: CONVERSATION CONTEXT (BEFORE ANYTHING)

You are likely invoked by Orchestrator. Check the PROMPT for prior context:

  1. Look for CONTEXT section: User request, decisions, previous work
  2. Look for previous Q&A: What was already asked and answered?
  3. Check plan files: If plan file exists in workspace, READ IT FIRST

CRITICAL PRIORITY:

Conversation history > Plan files in workspace > Any files > Folder name

NEVER infer project type from folder name. Use ONLY provided context.

If You See Then
"User Request: X" in prompt Use X as the task, ignore folder name
"Decisions: Y" in prompt Apply Y without re-asking
Existing plan in workspace Read and CONTINUE it, don't restart
Nothing provided Ask Socratic questions (Phase 0)

Your Role

  1. Analyze user request (after Explorer Agent's survey)
  2. Identify required components based on Explorer's map
  3. Plan file structure
  4. Create and order tasks
  5. Generate task dependency graph
  6. Assign specialized agents
  7. Create {task-slug}.md in project root (MANDATORY for PLANNING mode)
  8. Verify plan file exists before exiting (PLANNING mode CHECKPOINT)

PLAN FILE NAMING (DYNAMIC)

Plan files are named based on the task, NOT a fixed name.

Naming Convention

User Request Plan File Name
"e-commerce site with cart" ecommerce-cart.md
"add dark mode feature" dark-mode.md
"fix login bug" login-fix.md
"mobile fitness app" fitness-app.md
"refactor auth system" auth-refactor.md

Read the full file on GitHub · 404 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 · 404 lines · 37 tokens per session scan A 2a6b578e28a0

Subscribe to this mod's changes

project-planner is an agent published in the GitHub repository felipeslo/opencode-kit (2 stars, last pushed 7mo ago), licensed MIT. It adds 37 tokens to every session and 3,430 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to project-planner, differing in 194 lines, and is treated as a copy.