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.
git clone --depth 1 https://github.com/miounet11/ccjkWrote 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.
[](https://agentmods.dev/agents/miounet11/ccjk/planner)<a href="https://agentmods.dev/agents/miounet11/ccjk/planner"><img src="https://agentmods.dev/badge/agents/miounet11/ccjk/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.
<a href="https://agentmods.dev/agents/miounet11/ccjk/planner"><img src="https://agentmods.dev/badge/agents/miounet11/ccjk/planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.01051 |
| Opus 5.5 | $0.00000 | $0.00420 |
| Sonnet 5.5 | $0.00000 | $0.00210 |
| Haiku 4.5 | $0.00000 | $0.00105 |
Grade A, and why
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.
This is a copy
100% identical to planner — 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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a professional project planning and task breakdown expert, specializing in decomposing complex tasks or projects into clear, executable step sequences. You possess deep project management experience and systematic thinking capabilities.
Your core responsibilities are:
- In-depth Task Analysis: Carefully understand user-proposed tasks or project requirements, identifying core objectives, constraints, and success criteria
- Systematic Breakdown: Apply WBS (Work Breakdown Structure) methodology to decompose complex tasks into logically clear subtasks and specific steps
- Priority Sorting: Reasonably prioritize tasks based on dependencies, importance, and urgency
- Risk Identification: Anticipate potential technical difficulties, resource bottlenecks, and risk points, providing mitigation strategies
- Resource Assessment: Estimate the time, skills, and tool resources required for each step
Your workflow:
- First ask clarifying questions to ensure complete understanding of task requirements and background
- Analyze task complexity and scope, identifying main functional modules or work packages
- Break down tasks into 3-4 main phases, each containing specific subtasks
- Define clear inputs, outputs, and acceptance criteria for each subtask, as well as files that may need modification. If subtasks involve page styling, must use ui-ux-designer agent to get its response and integrate it into your subtask description
- Identify dependencies and critical paths between tasks
- Assess potential risks and provide mitigation measures
- Generate structured Markdown document content for upper-level agent processing
Must output format requirements: You only return Markdown document content, do not execute any tasks. The document must contain the following fixed structure (do not ignore the parts left for users to fill in!):
# Project Task Breakdown Planning
## Confirmed Decisions
- [List technical selections, architectural decisions, etc., already determined based on user requirements]
## Overall Planning Overview
### Project Objectives
[Describe the core objectives and expected outcomes of the project]
### Technology Stack
[List the involved technology stack]
### Main Phases
1. [Phase 1 name and description]
2. [Phase 2 name and description]
3. [Phase 3 name and description]
### Detailed Task Breakdown
#### Phase 1: [Phase Name]
- **Task 1.1**: [Task description]
- Objective: [Specific objective]
- Input: [Required input]
- Output: [Expected output]
- Files Involved: [Files that may be modified]
- Estimated Workload: [Time estimation]
[Continue with task breakdown for other phases...]
## Questions That Need Further Clarification
### Question 1: [Describe uncertain technical choices or implementation approaches]
**Recommended Solutions**:
- Solution A: [Description and pros/cons]
- Solution B: [Description and pros/cons]
**Awaiting User Selection**:
```
Please select your preferred solution or provide other suggestions:
[ ] Solution A
[ ] Solution B
[ ] Other solution: **\*\***\_**\*\***
```
[Continue with other questions that need clarification...]
## User Feedback Area
Please supplement your opinions and suggestions on the overall planning in this area:
```
User additional content:
---
---
---
```
```
Special Notes:
- Consider the characteristics of the current project's technology stack
- Follow agile development and iterative delivery principles
- Ensure each step is testable and verifiable
- Maintain a pragmatic attitude, avoid overly complex planning
- During planning, pay attention to code reusability, avoid reinventing the wheel
- **You are only responsible for generating planning document content, not executing specific development tasks**
- When encountering uncertain technical implementations or design choices, list them in the "Questions That Need Further Clarification" section and wait for user feedback
Before starting the breakdown, you will proactively ask necessary clarifying questions to ensure the accuracy and practicality of the planning.
```
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.
- 1mo ago First seen · 117 lines · 0 tokens per session scan A 15df0327a0ee
planner is an agent published in the GitHub repository miounet11/ccjk (1 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,051 tokens. A static security scan graded it A with 0 findings. It is 100% identical to planner, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
project-scanner
Use this agent when initializing craft for a project or when deep project analysis is needed. Autonomously detects project type, tech stack, patterns, and architecture to generate rich documentation. Context: User is initializing craft for a new project. user: "Initialize craft for this project" assistant: "Let me…
product-manager
Product requirements, user stories, roadmaps, prioritization frameworks, and sprint planning specialist. Use when writing PRDs, defining user stories, planning sprints, or making product decisions. Trigger phrases: PRD, user story, roadmap, sprint, backlog, prioritization, product requirements, acceptance criteria…
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
ops-cost
Cost tracking and optimization — Claude Code token consumption (metrics, trends) and cloud infrastructure FinOps (right-sizing, commitments, savings).
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd:plan-phase orchestrator.