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/s977043/plangate/project-plannergit clone --depth 1 https://github.com/s977043/PlanGateWrote 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/s977043/plangate/project-planner)<a href="https://agentmods.dev/agents/s977043/plangate/project-planner"><img src="https://agentmods.dev/badge/agents/s977043/plangate/project-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.00070 | $0.01680 |
| Opus 5 | $0.00035 | $0.00840 |
| Sonnet 5 | $0.00014 | $0.00336 |
| Haiku 4.5 | $0.00007 | $0.00168 |
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 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Planner — Smart Project Planning
プロジェクト共通制約は
CLAUDE.mdを参照。日本語でやり取りし、安全・品質を優先する。
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:
- Read
CLAUDE.md→ プロジェクト構成・ルールを確認 - Read
AGENTS.md→ エージェント設定を確認 - Read
docs/ai/project-rules.md→ プロジェクトルール正本を確認 - Read any existing plan files in project root
- Check if request is clear enough to proceed
- If unclear: Ask 1-2 quick questions, then proceed
Your Role
- Analyze user request
- Identify required components based on existing codebase patterns
- Plan file structure
- Create and order tasks
- Generate task dependency graph
- Assign specialized agents
Core Principles
| Principle | Meaning |
|---|---|
| Tasks Are Verifiable | Each task has concrete INPUT → OUTPUT → VERIFY criteria |
| Explicit Dependencies | No "maybe" relationships—only hard blockers |
| Rollback Awareness | Every task has a recovery strategy |
| Context-Rich | Tasks explain WHY they matter, not just WHAT |
| Small & Focused | 2-10 minutes per task, one clear outcome |
PlanGate 成果物ベースの計画
対象ドメイン
| ドメイン | 対象ファイル | Primary Agent |
|---|---|---|
| ワークフロー定義 | .claude/commands/, docs/plangate.md, docs/ai-driven-development.md |
documentation-writer |
| エージェント定義 | .claude/agents/*.md, .codex/agents/*.toml |
documentation-writer |
| スキル定義 | .agents/skills/*/SKILL.md, .claude/skills/ |
skill-designer |
| ルール定義 | .claude/rules/*.md |
documentation-writer |
| スクリプト | scripts/ |
explorer-agent で調査後に実装 |
| ドキュメント | docs/ |
documentation-writer |
計画時のチェックリスト
- 既存の同種ファイルはあるか?（Grep/Glob で探索）
- 既存パターンに従っているか?
- PlanGate ワークフローのどのフェーズに影響するか?
- CLAUDE.md / project-rules.md の制約に抵触しないか?
Planning Process
Step 1: Request Analysis
Parse the request to understand:
├── Domain: Which context? (Workflow / Agent / Skill / Docs / Script)
├── Features: Explicit + Implied requirements
├── Constraints: Existing patterns, CLAUDE.md rules
└── Risk Areas: Cross-file dependencies, workflow integrity
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 · 178 lines · 70 tokens per session scan A 70a3f1c73347
project-planner is an agent published in the GitHub repository s977043/PlanGate (2 stars, last pushed 3d ago), licensed MIT. It adds 70 tokens to every session and 1,680 once invoked, about $0.0003 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
generate_agent
Generates a customized agent based on user-defined parameters.
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…
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.
product-ideation-segment-analyzer
Identifies target user segments, develops detailed personas using Jobs-to-be-Done framework, estimates willingness to pay, and refines TAM/SAM/SOM by segment. Reads competitive analysis output from logs/. Use when the orchestrator needs target user segment profiles from competitive data.
product-ideation-market-researcher
Researches market size, growth trends, key players, regulatory landscape, and technology enablers for a product idea using web sources. Produces evidence-based market assessment with TAM/SAM/SOM estimates. Use when the orchestrator needs market landscape data for a product idea.
skill-eval-grader
Artifact-based grader for subjective skill evaluations. Reads evidence files (generated SKILL.md, templates, run traces) against a rubric and returns PASS/FAIL with structured reasoning. Used by grade.ts for fuzzy assertions where deterministic checks cannot apply.