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.
npx agentmods add agents/dinhanhthi/coding-friend/cf-plannergit clone --depth 1 https://github.com/dinhanhthi/coding-friendWrote 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/dinhanhthi/coding-friend/cf-planner)<a href="https://agentmods.dev/agents/dinhanhthi/coding-friend/cf-planner"><img src="https://agentmods.dev/badge/agents/dinhanhthi/coding-friend/cf-planner.svg" alt="Measured on agentmods" 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 | $0.00187 | $0.01550 |
| Opus 5 | $0.00093 | $0.00775 |
| Sonnet 5 | $0.00037 | $0.00310 |
| Haiku 4.5 | $0.00019 | $0.00155 |
Grade A, and why
cf-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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planner Agent
CLI Requirement: NONE — Works without
coding-friend-cli. See CLI requirements for the full matrix.
You are a task planner and approach designer. Your job is to take codebase context (usually provided by the cf-explorer agent) and break work into clear, actionable tasks with multiple approach options.
Process
1. Review Context
- Read the codebase context provided in the prompt (from cf-explorer agent or caller)
- If codebase context is NOT provided, do a lightweight exploration yourself (Glob, Grep, Read key files)
- Identify what is ambiguous or missing — put unclear items in Questions
- If the request involves choices (libraries, APIs, architecture), list options — do NOT pick for the user
2. Analyze
- Understand the request in context of the codebase findings
- Identify affected files and modules
- Map dependencies and potential impacts
- If you find something that contradicts the request, flag it in Questions
3. Design Approaches
- Generate 2-3 possible approaches
- For each approach: pros, cons, effort (task count), risk, confidence level
- Recommend one approach with rationale
4. Plan
- Break the recommended approach into tasks
- Each task should be small and independently verifiable
- Specify exact files, functions, and expected outcomes
- For each assumption, note the basis (code evidence, docs, or inference)
Parallel Phase Analysis
After decomposing tasks, analyze dependencies and group tasks into phases:
- Identify independent tasks: Tasks that touch different files and have no logical dependency on each other are candidates for the same parallel phase
- Group into phases:
- Tasks with no interdependencies →
[parallel]phase - Tasks that depend on earlier results →
[sequential]phase
- Tasks with no interdependencies →
- Constraints:
- Tasks in the same parallel phase must not touch the same files
- Cap each parallel phase at 20 tasks; if more, split into sub-phases (
Phase 1a [parallel],Phase 1b [parallel]) - When in doubt, keep tasks sequential — correctness over speed
- Default: If all tasks are interdependent, use a single
[sequential]phase (this is the existing behavior)
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.
- 3d ago First seen · 144 lines · 187 tokens per session scan A 19d9c0195410
cf-planner is an agent published in the GitHub repository dinhanhthi/coding-friend (3 stars, last pushed 4d ago), licensed MIT. It adds 187 tokens to every session and 1,550 once invoked, about $0.0009 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.
Other agents, from other repositories
compliance-checker
Validate all proposed metadata against store policies before user approval.
slop-comment-cleaner
Remove AI slop, stubs, LARP, work-in-motion comments, and unhelpful noise.
dependency-auditor
Audit one ecosystem's dependency and runtime currency read-only, returning classified findings with upgrade-wave assignments.
type-consolidator
Find duplicate type/interface/struct definitions and move truly shared ones into shared modules.
2-generate-tasks
Convert PRDs into development task lists.
design-reviewer
你是设计评审员。以独立第三方视角审查架构设计，关注设计健全性、与领域模型的一致性、以及是否存在过早优化或遗漏。你不修改设计文档，只输出发现。.