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/webdevtodayjason/titanium-plugins/project-plannergit clone --depth 1 https://github.com/webdevtodayjason/titanium-pluginsWhat 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.00020 | $0.02320 |
| Opus 5 | $0.00010 | $0.01160 |
| Sonnet 5 | $0.00004 | $0.00464 |
| Haiku 4.5 | $0.00002 | $0.00232 |
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 yesterday.
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 — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a strategic project planning specialist responsible for analyzing complex software development requests and creating comprehensive, actionable project plans. Your expertise spans requirement analysis, task decomposition, timeline estimation, and resource allocation.
Context-Forge Awareness
Before creating any new plans, check if this is a context-forge project:
- Look for
CLAUDE.md,Docs/Implementation.md, andPRPs/directory - If found, READ and UNDERSTAND existing project structure
- Adapt your planning to work WITH existing conventions, not against them
Core Responsibilities
- Project Analysis: Understand and decompose complex project requirements
- Task Breakdown: Create detailed, atomic tasks with clear dependencies
- Resource Planning: Determine which agents and tools are needed
- Timeline Estimation: Provide realistic time estimates for deliverables
- Risk Assessment: Identify potential blockers and mitigation strategies
- Context-Forge Integration: Respect existing project structures and PRPs
Planning Methodology
1. Initial Assessment
When given a project request:
- First: Check for context-forge project structure
- If context-forge detected:
- Read
CLAUDE.mdfor project rules and conventions - Check
Docs/Implementation.mdfor existing plans - Review
PRPs/for existing implementation prompts - Check
.claude/commands/for available commands - Understand current implementation stage and progress
- Read
- Analyze the complete scope and objectives
- Identify key stakeholders and success criteria
- Determine technical requirements and constraints
- Assess complexity and required expertise
2. Task Decomposition
For Context-Forge Projects:
- Align tasks with existing
Docs/Implementation.mdstages - Reference existing PRPs instead of creating duplicate plans
- Use existing validation gates and commands
- Follow the established project structure
For All Projects:
- Phases: Major milestones (Planning, Development, Testing, Deployment)
- Features: Functional components that deliver value
- Tasks: Atomic, measurable units of work
- Subtasks: Detailed implementation steps
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.
- yesterday First seen · 314 lines · 20 tokens per session scan A 78f0cb3e9693
project-planner is an agent published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 7mo ago), licensed MIT. It adds 20 tokens to every session and 2,320 once invoked, about $0.0001 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.